On export of data, the data synchronization setup defines which records are processed.
Data synchronization only applies to messages with an internal document as source document.
You can use these types of data synchronization:
Type |
Description |
All |
This is the standard data synchronization. All records that are found, based on the source document setup, are exported. No data synchronization setup is required for this. |
Table events |
You can use table events to log data changes. You can define, for each record, which table events are logged. The table events are logged in the Data synchronization log. From here, the logged entries must be processed further to the Outbound message queue. Process the outbound message queue to run the messages to export the records. |
Date range |
You can use a date range to export only the records that are changed or added since the latest message run. |
Name | Responsible | Description | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Set up data synchronization - Table events - Message |
Application Consultant |
On export of data, the data synchronization setup defines which records are processed. Data synchronization only applies to messages with an internal document as source document. This topic explains how to use table events to track data changes. You can define, for each record, which table events are logged. The table events are logged in the Data synchronization log. From here, the logged entries must be processed further to the Outbound message queue. Process the outbound message queue to run the messages to export the records. |
||||||||||||||||||||||
Set up data synchronization - Date range - Message |
Application Consultant |
On export of data, the data synchronization setup defines which records are processed. Data synchronization only applies to messages with an internal document as source document. This topic explains how to use a date range to export only the records that are changed or added since the latest message run. Make sure, the root record of the source document has a date/time field that indicates when the record is last changed, for example a 'modifiedDateTime' field. If you run the message, all records that are found, based on the source document setup, are considered. For each found root record, the date/time is compared with the Latest run date/time of the message. Only the records are exported with a date/time that is later than the latest run date/time of the message. |
||||||||||||||||||||||
Validate connectivity setup |
Application Consultant |
If you open a form or save (changes to) the setup of a key element in Connectivity studio, the setup is validated automatically. If errors are found in the setup, an error icon is shown. You can click the icon to show the related error messages. You can also manually start an automated test to check for errors in the setup. As a result, the found errors are shown. Also, the error icons are shown where applicable.
When errors are found, you can try to fix these errors automatically.
You can check and auto-fix errors for these key elements in Connectivity studio:
In this flow, in the activity steps, as an example, the validation is done for documents.
|
Name | Responsible | Description | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Set up data synchronization - Table events - Message |
Application Consultant |
On export of data, the data synchronization setup defines which records are processed. Data synchronization only applies to messages with an internal document as source document. This topic explains how to use table events to track data changes. You can define, for each record, which table events are logged. The table events are logged in the Data synchronization log. From here, the logged entries must be processed further to the Outbound message queue. Process the outbound message queue to run the messages to export the records. |
||||||||||||||||||||||
Set up data synchronization - Date range - Message |
Application Consultant |
On export of data, the data synchronization setup defines which records are processed. Data synchronization only applies to messages with an internal document as source document. This topic explains how to use a date range to export only the records that are changed or added since the latest message run. Make sure, the root record of the source document has a date/time field that indicates when the record is last changed, for example a 'modifiedDateTime' field. If you run the message, all records that are found, based on the source document setup, are considered. For each found root record, the date/time is compared with the Latest run date/time of the message. Only the records are exported with a date/time that is later than the latest run date/time of the message. |
||||||||||||||||||||||
Validate connectivity setup |
Application Consultant |
If you open a form or save (changes to) the setup of a key element in Connectivity studio, the setup is validated automatically. If errors are found in the setup, an error icon is shown. You can click the icon to show the related error messages. You can also manually start an automated test to check for errors in the setup. As a result, the found errors are shown. Also, the error icons are shown where applicable.
When errors are found, you can try to fix these errors automatically.
You can check and auto-fix errors for these key elements in Connectivity studio:
In this flow, in the activity steps, as an example, the validation is done for documents.
|
Related to | Notes |
---|---|
Run message |
  |
Process data synchronization log |
  |
Process outbound queue |
  |
Monitor data synchronization log |
  |
Troubleshoot data synchronization log issues |
  |