We have our own custom app (separate from Microsoft Dynamics CRM) that gets vcard data from Exchange, and ultimately sends the info into the CRM database as a Contact record.
We are now deploying the Outlook client. Have some questions.
We want to send Contact edits from the CRM back to the original vcard. However, seems this is not possible.
Here is the exact flow if I understand correctly.
1. Our custom app gets the Exchange data, and creates CRM contacts
2. The Outlook Client feature will result in a new vcard being created in the address book (assume we've configured the filters, etc). It will NOT update the already existing vcard. Therefore, from the user perspective a "duplicate vcard contact" is created.
Here is the question if the statements above are correct.
How do you provide the Outlook user an address book without duplicate vcards?
Does something like this make sense? I hope someone has some implementation best practices to share.
Step 1: assume that our custom app has gathered all of the necessary Exchange contact data, and that data now exists in CRM.
Step 2: go the user's machine, and as a precaution...archive their vcard data into a backup file. There are no vcards in the outlook contacts folder
Step 3: "turn on" the Outlook client. In theory, with the right filter the user's vcards will get pushed back into the Outlook address from the CRM database