Learn how to map custom resources and custom entities in the context of the integration between Adobe Campaign Standard and Microsoft Dynamics 365.
This capability is not available out of the box as part of the product. The implementation requires Adobe Consulting to be engaged. Please reach out to your Adobe representative to find out more.
The Microsoft Dynamics 365-Adobe Campaign Standard integration supports custom entities, enabling custom entities in Dynamics 365 to be synchronized to corresponding custom resources in Campaign.
The new data in the custom resources can be used for several purposes, including segmentation and personalization.
The integration supports both linked and non-linked tables. Linking is supported up to three levels (i.e., level1->level2->level3).
If any Campaign custom resource record contains personal information, specific recommendations apply. Learn more in this section.
When configuring custom entity data flows, it is important to be aware of the following:
Creating and modifying Campaign custom resources are sensitive operations which must be performed by expert users only.
For custom entity data flows, change tracking must be enabled within Dynamics 365 for synchronized custom entities.
If a parent and linked child record are created close to the same time in Dynamics 365, due to the parallel processing of the integration, there is a slight chance that a new child record could be written to Campaign before its parent record.
If the parent and child are linked on the Campaign side using the 1 cardinality simple link option, the child record will remain hidden and inaccessible (via UI or API) until the parent record arrives in Campaign.
(Assuming 1 cardinality simple link in Campaign) If the child record is updated or deleted in Dynamics 365, and that change is written to Campaign before the parent record shows up in Campaign (not likely, but a remote possibility), that update or delete will not be processed in Campaign and an error will be thrown. In the case of update, the record in question will need to be updated in Dynamics 365 again in order to sync the updated record. In the case of delete, the record in question will need to be taken care of separately on the Campaign side since there is no longer a record in Dynamics 365 to delete or update.
If you run into a situation where you believe you have hidden child records and no way to access them, you can temporarily change the cardinality link type to 0 or 1 cardinality simple link to access those records.
A more comprehensive overview of Campaign custom resources can be found in this section.