Avatar

Level 2

After changing the order of fields to synchronyze, I found a scenario that gave me more error info:

“Error while inserting the object with local ID '399932262', cause: 'Account With Id = 33a6ce18-def9-e711-a829-000d3ab4be81 Does Not Exist'.”

This is interesting, beceause I’m inserting a  letter activity from campaign to CRM.  This letter is to be connected to a contact. RegadingObjectId therefore is the id of the contact (contactid).

Yes! It is the Id mentioned in the errormessages. Strange thing about it is that the regardingobjecttype I configured to be synchronized is ‘contact’ but instead CRM throws an error on ‘account’.

So if CRM is trying to find  mentioned guid in the ‘account’ entity; it seems correct to throw an error, as it does not exist as account id; it is a contact id. In that case either campaign ignores the option given via  ‘regardingobjecttype’ (where in case of CRM 4.0 sync it works) or CRM ignores it and therefore somehow CRM thinks the regarding object is account in stead of contact.

1412804_pastedImage_0.png