Today's blog post was written by Keith Mescha, Principal Architect at Sonoma Partners.
Here at Sonoma, we are a big fan of KingswaySoft’s tools for data migration to Dynamics 365 and Salesforce. We use SQL Server Data Tools and SSIS all the time for data migrations and integrations to CRM for our clients. The tool set they provide is an add-on that allows us to quickly read and write data from the cloud. In one recent migration project, we ran into an odd issue that took a bit to figure out. Here's what happened...
Within the KingswaySoft CRM Online adapter, there is built-in functionality to do lookups for related fields based on text provided. This will allow you to provide the text value, and it will retrieve the GUID for you to populate in the target entity. In this case we were using this functionality for loading Opportunity Products and using text lookup for the Unit of Measure attribute. This attribute is required on this entity, but we are not really using Units of Measure so we just needed to retrieve the default ‘Primary Unit’ GUID.
So we wired this all up and started to push our data however nothing was happing. The process just appeared to hang, and we did not see any data show in CRM. No obvious errors were being returned by the KingswaySoft CRM adapter to tell us anything was wrong like we typically see. We started looking at plugins and workflows on the target org. We played around with various batch sizes, but still nothing was happening.
After some head scratching we decided to fire up Fiddler to see what we could find in the messages being sent between our process and CRM Online. We quickly noticed that we were getting 500 errors for every call to CRM. In digging into the messages, we were getting an error that ‘UoM entity does not contain attribute with Name = ‘statecode.’ This didn’t make any sense at first, but then we remembered there is an option in the Text Lookup function to Exclude Inactive and realized very quickly this must be our issue. So we unchecked this box, and our process started working and records migrated into CRM.
This seems like a defect in the product, and we will report a bug to KingswaySoft but figured if anyone else ran into similar issues this might be of some assistance.
The key takeaway here is that for data migrations with CRM Online, Fiddler is your friend for pulling the curtain back to see what’s really going on with some of the calls that the data migration tool set might be gobbling up and not exposing. Oh and don’t check this box if using Text Lookup on the UOM entity as there is not a statuscode field on that entity in CRM apparently.