Multi-source sync allows you to bring information from multiple sources into a single, centralized destination table. The records residing in each of the sources are aggregated together in the destination table.
This article will walk you through the basic setup of multi-source sync, and then introduce you to some core concepts to better understand all of the features. We’ll then cover a more advanced example and additional considerations to help you think through how to best use this robust feature.
To setup multi-source sync you’ll need to already have one synced table created.
If you’ve never set up a sync before, we recommend reading through our Sync - Basic setup
article found here. Becoming comfortable with the way syncs work will help you understand the more advanced topics covered in this article.
Once a synced table is already created, you can add other sync sources by opening the sync configuration menu. To do this, click the dropdown arrow next to your synced table, and select “Update sync configuration”.
The “Add records from another source” option will appear in the synced table settings. Clicking this option will allow you to configure another source to sync from.
Click “Add records from another source” to bring up the sync configuration window. Then choose the base, table, and view that you are looking to aggregate with the existing synced table. Click “Next” after choosing these options.
Lastly, navigate through the field mapping menu and decide what works best for your individual setup. We cover more about field mapping in the next section.
For the purpose of syncing in Airtable, a source is the origin where the synced data is coming from. Within Airtable, a source is a shared view with syncing enabled. We plan to continue adding external sources over time as well. So a source can be any place where the data is coming from.
The main difference between single and multi-source syncs is that multi-source syncs require field mapping. Since data in a destination table’s fields can be provided by multiple sources, your choices during the sync setup process will determine how the source fields map to the destination’s synced fields. For example, if a field in one source is formatted differently than a field in another source, then the field mapping setup allows you to determine both where the data will be populated in the multi-source destination synced table as well as how it is formatted.
From the image above you can see that some fields were automatically mapped, while others were mapped manually. In particular, notice that the “Completion date” (single line text) field’s information has been mapped to the “Due date” (Date field), thus converting the field type to match the date field format of the primary source.
When adding a new source, we will try and match column names to existing column names. For columns that could not be matched, the default option will be to sync that data to a new field on the table instead. You can change any mappings or opt to sync any source field to a new synced field.
The primary source for a field is what will determine:
- The field type and configuration
- Whether the field is removed when the source field is hidden or destroyed.
For a sync with a single source, you can consider the single source to be the primary source for all fields. Whichever source first maps to a field, either when setting up the first source or by choosing the "Sync to a new field" option, becomes the primary source for that field. For every synced field you can change the primary source from the sync configuration window:
In this image, you can see that changing the “Due date” field’s primary source changes the field type from a date field to a single line text field or vice versa.
Not all bases will have the exact same setup. Field name and type differences may need to be accounted for during the field mapping process. In this example, we have three different teams’ (Product, Marketing, and Engineering) projects being aggregated into a single, high-level overview for management to see.
Let’s start from the beginning. None of the bases are connected to each other via Airtable Sync.
Enable syncing in source views
First, make sure to check that the “Data in this view is allowed to be synced to other bases” option is toggled on in every view source that you intend to aggregate.
Choose a base whose configuration makes the most sense for your workflow. You can always change this later, but remember that the first source you sync will default to be your primary source as well as determine the initial naming structure for the fields.
Sync each base to the destination base
Next, you will need to sync each base to the destination base. There are multiple flows to choose from when looking to sync. For this example, we will set up our syncs from the “Management” destination base. As you can see below, the name of this newly created synced table will take on the name of the view that it has been sourced from. Feel free to rename the table and any synced fields after this initial setup.
This process will need to be repeated for the other sources you want to sync. Notice that some fields will automatically map, while others will show the option to “Sync to a new field type.” This means that a new field would be created. For our example, we choose to manually map the fields from the Product base to fields already created from the initial sync setup.
Now, to add a third source from the engineering team’s base.
Now that we have the three sources syncing to the Management base we can always go back and tweak the setup if changes are needed down the road.
After a sync is created, users have the following options for every source field. These options can be found in the “Update sync configuration” window.
Select a new synced field in dropdown
Change the destination synced field for the source field of your choice. The type of the destination synced field will also change based on the primary source field.
Uncheck a field
stop syncing data from this source to the mapped field. If this source was the primary source the synced field will also be destroyed.
Select ‘Sync to new field in the dropdown
If the field was previously mapped to a destination:
- If the source was primary - the synced field will be destroyed, and the data will be mapped to a new field instead.
- If the source was not primary, the data from this source will be mapped to a new field instead.
If this field was previously unmapped - the data in the source field will be mapped to a new synced field.
How do I see what source a row is syncing from?
There isn’t currently a good way to see this visually, but we’re working on it. For now, you can use the Open Source Record button action to open the record in a new tab.
How is the column type determined when multiple sources are involved?
The primary source determines the column type.
How do I see which source is the primary source?
Navigate to the sync configuration window and select the change button next to the “Advanced field options” row.