Synchronise data objects
Overview
In this destination service, DinMo will sync any data object, and keep them up to date in Microsoft Dynamics 365.
To do so, you will need to go through these three steps:
Creating a MD365 destination. Refer to the corresponding section for more info.
Creating a segment composed of all the users that will populate your MD365 object. Refer to this step-by-step tutorial to learn how to build segments without SQL in DinMo.
Activating the segment to the MD365 destination to start sending data.
Every time the activation runs:
DinMo performs an upsert operation:
Insertion: If an object does not exist, DinMo will create it using the mapped attributes and object ID value.
Update: If an object exists, DinMo updates only the mapped attribute values.
Attributes that exist will have their values updated.
Attributes not present in the object will be created upon the first synchronisation and regularly updated afterward.
DinMo will not delete existing objects even if the record no longer exists in the model or segment. It will simply stop updating these rows.
Destination setup
To start exporting objects, you are first required to create a MD365 destination with the corresponding destination service.
You will need to specify whether you want to:
Update an existing data object
Create a new data object
Note: if the existing data objects do not appear, then your app does not have the necessary permissions
Activation configuration
Once the destination has been setup, and your DinMo model or segment is created, you can create an activation to start sending data to MD365 right away.
Fields mapping
In the Fields mapping section, you are asked to specify the field contained in your DinMo model corresponding to the primary key of the target data object. This field will be used to link the model's records to existing records in MD365.
The primary key you must choose can be either of:
GUID: Auto-generated primary key from your existing tables in MD365
Alternate keys: Custom unique identifier created in DinMo
You can then map any other attribute existing in MD365. These attributes will then be updated by DinMo during each activation.
Custom Attributes
In this section, any field you select will be automatically created and exported as a new column in your data object. The associated field will have the same name in MD365 and DinMo.
The values of the attributes selected here will then also be updated at each activation.
Scheduling
In this section, specify how often the data should be updated in MD365. Every time the object is updated:
Any new record having entered your DinMo model or segment since the last update will be added to your MD365 object
Any user having left your DinMo model or segment since the last update will be removed from your MD365 object
Last updated