You can synchronize tables from Microsoft Dynamics 365 to Campaign and Campaign marketing metrics to Microsoft Dynamics 365. Synchronization is executed through three dedicated technical workflows: Microsoft Dynamics 365 to Campaign, Campaign to Microsoft Dynamics 365, Opt-In/Out. Refer to this section to learn more.
You need to stop/start the Microsoft Dynamics 365 to Campaign workflow to have your changes taken into account. Learn more
The Microsoft Dynamics 365 to Campaign page shows a list of entities in Microsoft Dynamics 365 and the custom resources in Adobe Campaign they will be synchronized with. You can add new mappings, edit or delete existing mappings.
Here is a description of each of the columns in this table:
MICROSOFT DYNAMICS 365 TABLE: this column identifies which entity in Microsoft Dynamics 365 will be the source of data for the mapping.
CAMPAIGN TABLE: this column identifies which resource in Adobe Campaign will be the destination of data for the mapping.
ACTIONS: possible actions are listed below:
Click the Edit icon to edit this mapping.
Use the Delete icon to delete a table mapping.
Click the Replay Data icon to re-synchronize all the data in the Microsoft Dynamics 365 table. Normally the integration application will only synchronize the data in Microsoft Dynamics 365 that has changed recently. However, in some cases (e.g., you’ve made a change or made a mistake) you might want all the data to be re-synchronized. In these cases, you would click this button and, the next time you stop/start the Microsoft Dynamics 365 to Campaign workflow, your data would start to synchronize.
If you click on the Replay Data button and the checks are successful, the icon will become disabled: it indicates that the data for this table mapping pair will be re-synchronized with the next execution of the Microsoft Dynamics 365 to Campaign workflow.
You cannot select to replay the data when the following are true:
The number of records that need to be re-synchronized varies. If you have a large number of records, it can take some time to complete the synchronization process. Refer to the Backlog metric in the Workflows page as the integration application works to complete the syncing process.
It is strongly recommended you stop the integration workflow when publishing changes to either Adobe Campaign Standard or Microsoft Dynamics 365. Applicable changes include: updates to resources/entities (and their associated fields), links, identifier columns, etc. that are currently in use by the integration.
To create a new mapping, follow the steps below:
in the Microsoft Dynamics 365 to Campaign page, click the Add New Mapping button.
Use the drop-down lists to select Microsoft Dynamics 365 and Campaign tables to map.
Most of the other inputs on the page will be dependent on which tables you choose.
You cannot map each table more than once. Therefore, you will notice that the dropdown selections will not include tables that have already been mapped.
Click OK to confirm: the application will need a brief moment to read in field information associated with the selected tables.
You can then proceed with the mapping configuration. Learn more
You can only choose the tables in this page when you are first adding the mapping. Make sure that you have selected the correct tables before clicking the Save button: once saved, the table selection fields will be read-only.
If you edit an existing mapping then you will see that the table selections are not editable.
This is by design because the inputs further down in the page are based on the fields associated with these tables. Changing the tables would make all the fields associated with these tables invalid. If you want to change the table to map to, you will need to return to the previous page, delete the mapping you want to change, and add a new mapping.
In this section you will learn how to configure a single mapping of one Microsoft Dynamics 365 table to one Adobe Campaign table.
You can define the following settings:
When adding a new Microsoft Dynamics 365 to Campaign table mapping, you need to identify the ID field.
The Microsoft Dynamics 365 primary key is read-only because the application will detect it.
For Campaign, you need to select which field will be the unique key. It must be configured as a CRM ID custom resource and must have no duplicates.
You will only be able to choose the ID field on the table when you have selected Add New Mapping. If you click the edit button to edit an existing table mapping then the ID field will be read-only.
The primary keys will always be the first field names listed in the Field Mappings section. As a reminder, the following icon is listed to the right to remind you that these are the primary keys.
The Field Mappings section allows you to add field mappings other than the Primary Keys. To add a new mapping of a field from Microsoft Dynamics 365 to Adobe Campaign, click the Add new field mapping button.
Select Microsoft Dynamics 365 and Campaign fields in the lists:
These lists contain the field names that are associated with the Microsoft Dynamics 365 and Campaign tables you have selected at the top of the page.
The Apply updates switcher allows you to control whether updates to this field will be propagated from Microsoft Dynamics 365 to Campaign:
If it is switched on , updates to the value(s) in Microsoft Dynamics 365 will be propagated to Adobe Campaign as the updates occur.
If you switched off , the value will be propagated when data is initially loaded (or replayed), but incremental updates to the field in Microsoft Dynamics 365 will not be propagated.
Click on the Apply updates column heading to update all of the switches to on or off.
When you select field values, you will see the data type show up below the drop down menus. This is something to keep in mind when mapping values from one field to the other.
You cannot map multiple Microsoft Dynamics 365 fields to a single Campaign field.
Use the Add New Field Replacement button to define a new field replacement.
Field replacements allow you to identify:
A dropdown list will be provided for picklist, enumeration, and boolean values. A text box will be used for other string and numeric types.
Use the Add New Filter button to select which Microsoft Dynamics 365 records will be propagated to Campaign. You can choose any field associated with a record to add to filters (the field name does not need to be added to the field mappings).
You specify a filter by filling out the following information:
You can choose how these filters are evaluated by setting the input labeled Choose the filter comparison operator. If you choose And, all of the filters must be true for a record to get propagated to Campaign. If you choose Or, the record will get propagated if any of them evaluate to true.
The option Do you want to delete records in Adobe Campaign Standard that will be filtered out from Microsoft Dynamics 365? controls whether you want records that have filtered out to be deleted from Campaign. If you select No then the records will remain in Adobe Campaign. Select Yes to have them deleted by the integration logic.
If no filters are added, all records that have been modified will be propagated to Adobe Campaign.
You can set up the following additional options when configuring a mapping:
Set the Apply deletes in Microsoft Dynamics 365 to Campaign? option to Yes, if you want to propagate deletions that occur in Microsoft Dynamics 365 to the corresponding field in Adobe Campaign (based on the field name mapping). Select No to ignore deletions in Microsoft Dynamics 365.
Set the Use technical values in Microsoft Dynamics 365 picklists? option to No if you want to propagate to Campaign the display value associated with a Microsoft Dynamics 365 picklist. Select Yes to propagate the technical value.
The Campaign to Microsoft Dynamics 365 page allows you to identify which email marketing events will be mapped from Adobe Campaign to Microsoft Dynamics 365.
The four metrics that you are able to control are: Sends, Clicks, Opens, and Bounces.
Select Yes to confirm that you do want events of that type to flow to Microsoft Dynamics 365.
Click here for more information on these email event flows.
The Opt-In/Out workflow allows you to identify the flow of the opt in/out information between Microsoft Dynamics 365 and Adobe Campaign. This assumes that the data is associated with the Microsoft Dynamics 365 entity “contact” and the Adobe Campaign resource “profile”.
Learn more about Opt-out management in this section.
Remember that you need to click “Save” to save your selections. Also remember that you must stop the Campaign to Microsoft Dynamics 365 workflow and then click play for the integration to incorporate your changes.
Below is the list of available options for synchronizing data:
Disabled: when this option is selected, no opt in/out information will move between Adobe Campaign and Microsoft Dynamics 365.
Unidirectional (Microsoft Dynamics 365 to Campaign): this option is used to flow opt-in/out from Microsoft Dynamics 365 to Adobe Campaign only. The integration application will not let you configure the flow in this screen; instead, click the Save button, and navigate to the Microsoft Dynamics 365 to Campaign workflow. In this workflow, you can edit the contacts/profile table mapping to identify how you want your opt-in/out fields to map.
Unidirectional (Campaign to Microsoft Dynamics 365): this option will make visible the Mappings section. These inputs will allow you define which Adobe Campaign fields will map data to what fields in Microsoft Dynamics 365. This means that if you happen to manually update a value in Microsoft Dynamics 365 then its value would be overwritten by the Adobe Campaign value if it happens to change.
Bidirectional: this option will make visible the Mappings section. These pairs will identify which fields in Microsoft Dynamics 365 and Adobe Campaign will map to each other. Learn more.
This section only applies when the Opt-in/out synchronization direction field is set to Unidirectional (Campaign to Microsoft Dynamics 365) or Bidirectional. You can define which fields in Microsoft Dynamics 365 map to what inputs in Adobe Campaign.
The Microsoft Dynamics 365 field names include all of those that are of type boolean.
The Adobe Campaign field names are a fixed set of values specific to opt-in/out. The Adobe Campaign field names are a fixed set of values specific to opt-in/out. The set of values in this list cannot be changed.