1. To-Increase Dynamics 365 for Finance & Operations
  2. Connectivity studio
  3. Operation
  4. Integration processes

Data synchronization process

This flow shows a typical example of a data synchronization process.


D365 FO D365 FO Start Start Events are logged in the Data synchronization log Events are logged in the Data synchronization log For messages and web service actions, you can use table events to track data changes. You can define, for each table, which table events are logged. The table events are logged in the Data synchronization log. Data synchronization log is processed

Process data synchronization log process

When you process the data synchronization log, automatically several actions are done, and several decisions are made based on the applicable setup. This flow shows the automatically executed actions and decisions when the data synchronization log is processed.

 Outbound queue is processed Outbound queue is processed For messages and web service actions, you can use table events to track data changes. You can define, for each table, which table events are logged. The table events are logged in the data synchronization log. On processing the data synchronization log, based on the logged events, records are added to the outbound queue. On processing the outbound queue, for each record, the related message or web service action is run to export the applicable data. Message or  web service action  triggered by  outbound queue? Message or  web service action  triggered by  outbound queue? Message is processed

Message process

This flow shows a typical example of a message process.

Example

Import customers from a webshop to D365 FO. In this case, the webshop is the source and D365 FO the target.


For both the source (webshop) and the target (D365 FO) a connector and a document are required. Also, a message is required to map the source and target data.

 Outbound web service is processed

Outbound web service process

The outbound web service process is used to request data from an external application and to process the response in D365 FO, via an external web service.

Only D365 FO can trigger an outbound web service action. When triggered, the outbound web service action automatically runs the defined messages.
This flow shows a general overview of the outbound web service process that is started when an outbound web service action is triggered.

 End End Message Web service action

Activities

Name Responsible Description

Events are logged in the Data synchronization log

D365 FO

 		For messages and web service actions, you can use table events to track data changes. You can define, for each table, which table events are logged. The table events are logged in the Data synchronization log.

Data synchronization log is processed

D365 FO

 		When you process the data synchronization log, automatically several actions are done, and several decisions are made based on the applicable setup. This flow shows the automatically executed actions and decisions when the data synchronization log is processed.

Outbound queue is processed

D365 FO

For messages and web service actions, you can use table events to track data changes. You can define, for each table, which table events are logged. The table events are logged in the data synchronization log. On processing the data synchronization log, based on the logged events, records are added to the outbound queue. On processing the outbound queue, for each record, the related message or web service action is run to export the applicable data.

Message is processed

D365 FO

 		This flow shows a typical example of a message process.

Example

Import customers from a webshop to D365 FO. In this case, the webshop is the source and D365 FO the target.


For both the source (webshop) and the target (D365 FO) a connector and a document are required. Also, a message is required to map the source and target data.

Outbound web service is processed

D365 FO

The outbound web service process is used to request data from an external application and to process the response in D365 FO, via an external web service.

Only D365 FO can trigger an outbound web service action. When triggered, the outbound web service action automatically runs the defined messages.
This flow shows a general overview of the outbound web service process that is started when an outbound web service action is triggered.

Process data synchronization log process

Provide feedback