Multi-source syncing overview
  • 01 May 2024
  • 7 Minutos para leer
  • Oscuro
    Ligero
  • PDF

Multi-source syncing overview

  • Oscuro
    Ligero
  • PDF

The content is currently unavailable in Spanish. You are viewing the default English version.
Resumen del artículo

Plan availability

Business and Enterprise Scale plans only

Permissions

  • Owners/Creators - Can create, modify, delete, and run syncs in the base(s) they have access to.

  • Editors - Edit records in source or target bases that they have access to as base or workspace collaborators. Additionally, editors can manually run syncs in the target base(s) to which they have access.

Platform(s)

Web/Browser, Mac app, Windows App, and the Airtable iOS and Android mobile apps

Related reading

  • Sync overview - For more information on general feature behavior and plan limits.

  • Airtable Sync - Basic setup - If you've never interacted with the Airtable Sync feature before, then it's important to read this article first to learn the basics.

  • Sync permissions - General information about how permissions relate to Airtable Sync.

Airtable terminology

  • Source - A single-source-of-truth dataset that is synced elsewhere in Airtable. You can think of this as the master dataset.

  • Target - A table that has been set up to sync with the source. An indirect relationship with other targets is also established when setting up a two-way sync. Interfaces in targets can be set up to permit edits that will sync back to the source.

Understanding multi-source sync concepts

Multi-source sync allows you to connect multiple bases. 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.

Source

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.

Field mapping

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.

1500006744161fieldMapping1.gif

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.

Note

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.

Primary source

The primary source for a field is what will determine:

  1. The field type and configuration

  2. 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:

1500006586842primarySource1.gif

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.

Adding multiple sync sources

To set up 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 Airtable Sync - Basic setup article. Becoming comfortable with the way syncs work will help you understand the more advanced topics covered in this article.

  1. 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”.

    1500006982621updateconfig.png

  2. 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.

    1500006982641addfromsource.png

  3. 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.

    1500006982661options.png

  4. 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.

    1500006801762overview.gif

Setting up a multi-source sync from scratch

Not all bases will have the same setup. Field name and type differences may need to be accounted for during the field mapping process. In this example, we have projects from three different teams (Product, Marketing, and Engineering) being aggregated into a single, high-level overview for management to see.

1500006743961Frame1.jpg

Let’s start from the beginning. None of the bases are connected via Airtable Sync.

Step 1: 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.

1500006588082viewshareSync.jpeg

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.

Step 2: 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.

1500006587742advancedMultiSync1.gif

Step 3: Repeat the sync source configuration process

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.

1500006743361advanced2.gif

Now, to add a third source from the engineering team’s base.

1500006586922advanced3.gif

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.

Sync source

The Sync source option allows you to see where the synced data is coming from. When this option is toggled on it will populate your destination table with a new field that shows the name of the view source that each record in the synced table comes from. When you create a new sync, this option will default to being turned on.

1500006743381syncSource1.gif

Note

If you would like to be able to quickly navigate to the original source record, then setting up an “Open source record” button field is useful.

Additional multi source sync considerations

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.

1500006586182other2.jpg

Uncheck a field

This option will stop syncing data from this source to the mapped field. If this source was the primary source the synced field will also be destroyed.

1500006743221other1.jpg

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.

1500006743441other3.gif

FAQs

Is there a limit to how many sync sources or synced tables I can have within my base?

You will have different limits for your synced tables according to the plan of the workspace your base belongs to. See our pricing page for more details on the sync limits for your workspace's plan.

How do I see what source a record is syncing from?

To visualize which source a record is syncing from, you'll want to enable the Sync source option in the Advanced field options menu. To navigate to a specific record from a source, you can use the Open Source Record button action to open the record in a new tab.

How is the field type determined when multiple sources are involved?

The primary source determines the field 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.


¿Te ha sido útil este artículo?