---
title: "Set up data synchronization - Table events - Message"
slug: "set-up-data-synchronization-table-events-message"
description: "Learn how to set up data synchronization, log table events, and manage outbound message queues for efficient data export in your system."
tags: ["Task topic"]
status: "update"
updated: 2026-10-16T10:05:47Z
published: 2026-10-16T10:05:47Z
canonical: "docs.staedean.com/set-up-data-synchronization-table-events-message"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up data synchronization - Table events - Message

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.

### Steps

1. Click **Connectivity studio - Integration Design**.
2. On the **Message** tab, in the list, find and select the desired message.
3. Click **Edit**.
4. Click **Header**.
5. Expand the **Setup for data synchronization** section.
6. In the **Synchronization type** field, select '**Table events**'.
7. Click **Save**.
8. In the outbound message queue, several entries can exist for a unique message. On processing the outbound message queue, by default, all entries for a unique message are bundled in one message run, which results in one file. You can choose to not bundle outbound message queue entries.

Select **No** in the **Bundle outbound queue by message** field.
9. Each table event that occurs to a record is logged in the data synchronization log for that record and related table. On processing the data synchronization log, by default, log entries for a child record of the source document are 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. If **Redirect event** is:
  - **Yes**, 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.
  - **No**, the sales line record is added to the outbound message queue. As a result, only the logged sales line and the sales order are exported. You can choose to not redirect events to the root record.

In the **Redirect event** field, select an option.
10. Sub-task: Add records.
  1. You can initialize the table event records based on the source document records. For each source document record, a record is added.

Click **Initialize**.

> [!NOTE]
> **Note**
> 
> You can also add table event records manually. To do so, click **New**. You can only select a record from the source document.
  2. For each added record, define the applicable settings.

In the list, find and select the desired record.
  3. Decide if you want to log record inserts for the record.

Select or clear the **Insert** check box.
  4. Decide if you want to log record updates for the record.

Select or clear the **Update** check box.
  5. Decide if you want to log record deletions for the record.

Select or clear the **Delete** check box.
  6. If the **Update** check box is selected, decide if you want to restrict data synchronization log processing (outbound queue creation) to only include the fields as defined for the record in the source document. Select or clear the **Check used fields** check box. If the **Check used fields** checkbox is:
    - Selected, only changes to the fields of the source document record are processed.
    - Cleared, all changes to the record are processed.
  7. Define the desired type of the table event triggers:
    - **SQL trigge**r: You can generate the SQL triggers in your database. So, no custom coding is required in the database.
    - **Event handler**: You must add custom code to the related tables for each selected event. This results in a better performance and can be useful for transactions like sales orders.

In the **Trigger type** field, select an option.
11. Sub-task: Create SQL triggers.
  1. If you have records with the **Trigger type =** '**SQL trigger**' selected, create the SQL triggers.

Click **Create SQL triggers**.

> [!NOTE]
> **Note**
> 
> To view the created SQL triggers, click **SQL** **trigger**. All existing SQL triggers are shown. For each SQL trigger, you can view in which messages or outbound web service actions it is used. To do so, on the **SQL triggers** page, click **Where used**.
12. Close the page.

## Related

- [Develop custom event handler](/develop-custom-event-handler.md)
- [Process data synchronization log - Connectivity Studio](/process-data-synchronization-log-cs.md)