23
Hi,
I'm migrating from our legacy ERP to D365 and am running into difficulty whilst creating a CE Case/Incident. I'm using an SSIS package to perform the migration. I can successfully create the Case but the 'Contact' field is not getting populated even though I'm providing a valid GUID for the primarycontactid. Is there some trick I need to be aware of when populating the Contact field or does it need something other than the contact id?
Thanks
Hello,
Yes, I'm using the KingswaySoft toolkit to connect to the D365 data. I configure the package so that all my transform logic is completed in a source SQL view and this feeds into the KWS component. The resulting actions are then directed to either an error log table or a success log table. Within the KWS component I had tried these configurations for the primarycontactid destination field:
I do however think that I have managed to resolve the issue. It turns out that whatever I pass into this field is overwritten by the Account Address 1 Contact field. In my earlier attempts to create a Case/Incident via KWS this field on the Account record was blank and so the new Case/Incident was also blank. I subsequently added a Contact to the Account and then when I created a Case/Incident the value was automatically added, regardless of what I provided in my source.
Does knowing what happens help anyone to understand the process and could therefore help me understand?
Hi,
If you are using Kingswaysoft tool then Alternate key can be used for lookup mapping
Moved to the Dynamics 365 Sales forum.
#1
Holly Huffman
103
#2
Muhammad Shahzad Sh...
96
Most Valuable Professional
#3
Gerardo RenterÃa Ga...
51
Most Valuable Professional
Share
Report
All responses (
Answers (
