Understanding Routes
In Data Mission Sync, each table you synchronize is called a 'route' — representing the data path from Dataverse to your Azure SQL database. When you select a table for synchronization, you're creating a route that defines what data flows from source to target.
Source Tables List
The Source Tables section shows all tables configured for synchronization. Click '+ Add Source Table' to add new tables.
| Column | Description |
| Logical Name | The Dataverse table's logical name (e.g., account, contact, lead). |
| Status | Whether synchronization is Enabled or Disabled for this table. |
| Initial Sync Completed | Shows 'Yes' if the first full sync has completed, 'No' if pending. |
| Actions | Menu (⋮) with options to manage the table configuration. |
Adding Tables
Click '+ Add Source Table' to open the Add Source Tables dialog. Use the search field to find tables by display name or logical name. The dialog shows tables available in your connected Dataverse environment.
Select one or more tables using the checkboxes, then click 'Add X Tables' to add them to your profile. Tables already configured in this profile do not appear in the list.
Each table in the list displays:
| Element | Description |
| Display Name | The friendly name of the table (e.g., 'Activity File Attachment'). |
| Logical Name | The system name used by Dataverse (e.g., 'activityfileattachment'). |
| Warning Icon | Tables showing ⚠ 'Enable change tracking to use this entity' require an administrator to enable change tracking in Dataverse before they can be synchronized. |
| 💡 Note: Tables that are already configured for synchronization in this profile do not appear in the list. | |
Adding Tables After Initial Setup
When you add a new table to an existing profile, Data Mission Sync automatically triggers a full sync of that table immediately. This behaves the same as the initial sync during profile creation — all records from the table are copied to your Azure SQL database.
For large tables, you may notice additional scheduled syncs for that table appearing in the Run History. This is normal behavior — these syncs are queued behind the initial full sync and will process incrementally once the initial sync completes.
| Adding tables to an existing profile does not affect tables that are already synchronized. Only the newly added tables will perform a full sync. |
Change Tracking Requirement
Data Mission Sync uses Dataverse's change tracking API for efficient incremental synchronization. Tables without change tracking enabled cannot be synchronized.
Tables showing a warning icon (⚠) with 'Enable change tracking to use this entity' require a Dataverse administrator to enable change tracking before they can be synchronized.
Enabling Change Tracking
To enable change tracking on a table:
1. Sign in to make.powerapps.com or the Power Platform Admin Center
2. Navigate to Tables and select the table you want to sync
3. Go to Properties or Table Properties
4. Enable the 'Track changes' option
5. Save the table
After enabling change tracking, the table will appear without a warning in Data Mission Sync.
Recommended Starting Tables
If you're new to Data Mission Sync, we recommend starting with a few commonly-used tables to verify your configuration:
| Table | Description |
| account | Companies, organizations, or business accounts. A core CRM table. |
| contact | Individual people associated with accounts. Another core CRM table. |
| lead | Potential customers or sales opportunities. |
| opportunity | Sales opportunities with revenue potential. |
Once you've verified synchronization is working correctly with a few tables, you can add additional tables as needed.