Monitor data synchronization log
Activity Flow

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.
This topic explains how to monitor 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.

When the logged events are processed, for each applicable message or web service action, a record is added to the Outbound queue.

If logged events in the data synchronization log are not processed to the outbound queue, you can:

• Check if processing the data synchronization log is set up correctly.
• Test the data synchronization log processing, which is explained in this topic.

When tested, a logged event is processed to the outbound queue. If processing a logged event goes:

• Fine, a record is added to the outbound queue. But, different from normal processing, the logged event stays in the data synchronization log.
• Wrong, no record is added to the outbound queue.

When the test is finished, you can view the processing steps and result in the message details. For each message or web service action that is subscribed to events of the same table, you can view the processing steps. In case of errors, verify the processing steps to see where the issue occurred.

This picture is an example of message details, with an explanation of the different parts:

Explanation:

1. The type of the logged event.
2. The message or web service action that is subscribed to events of the table.
3. The checks that are done to see if the logged event is valid for the message:
   • In case of an update: Is the field for which a value is changed defined in the source document of the message?
   • Is the company for which the event is logged defined as source company for the source connector of the message?
4. In the example, on the message, for the data synchronization setup, the Redirect event field is set to Yes. This means, on processing the data synchronization log, if the event is logged for a child record of the source document, it is added to outbound message queue for the root record of the source document. Example: The source document has a root record 'Sales order' and a child record 'Sales line'. A table event is logged for a sales line. The sales order record is added to the outbound message queue instead of the logged sales line record. As a result, the sales order and all its sales lines are exported by the message.
5. The message if no record is added to the outbound queue. In no record is added to the outbound queue, also a Query info section is shown. This section shows the query that is applied.
6. A summary of the result of the test.