My fellow CRM colleague Salim Adamon provided here a list of some of the available resources for each of these options. What if you are required keeping the SFDC number?ġ) Create a custom auto-numbering solution leveraging a new sequence/auto-number entity as well as synchronous/real-time workflows.Ģ) Create a custom auto-numbering solution using transactional plugins.ģ) Create a custom solution that leverages Auto-numbering web services What if you are required to migrate objects which the Dynamics CRM counterpart does not support auto-numbering? The platform will not let this happen and will always create its own auto number. In case you want to migrate Cases from SFDC to Dynamics CRM, you will not be able map the SFDC auto number field to the Dynamics CRM Case number (auto-number) field one and keep the SFDC value. In the table below, I will go a little deeper and provide further details about the implementation workaround that will be necessary in order to migrate some of the SFDC field data types: SFDC Data Typeĭynamics CRM auto-numbering feature is only available for some OOB entities (Contracts, Cases, Articles, Quotes, Orders, Invoices, Campaigns, Categories and Knowledge Articles). I also provided the level of complexity for each type of mapping and some hints about how to implement the SFDC concepts/features into Dynamics CRM so a data migration can take place. In Part 1 of this post, I enumerated all the SFDC field data types and how they map to Dynamics CRM field data types.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |