Synced field names won’t match if the same field name is added to a target before it’s added in the source base.New fields will merely enrich existing synced data like any other sync setup. Explanation: New fields can be created in target tables, but they will not be “syncable” back to the source.We cover more on permissions and Two-way sync here. As a reminder, individual field-level editing permissions can be set across the view you are using as the sync source. Specific fields - Only certain fields in the source will be available for syncing.Īn editable field is any field within a table that is not locked.Additionally, editable fields added in the source table will be editable in any target tables in the future. All editable fields - All editable fields in the source table will be editable in the target table.
There are two options below this toggle to consider: If this toggle is not enabled, then two-way syncing cannot occur. The main, and very important, difference with two-way syncs is that you need to enable the option Allow edits from other bases. In general, you can follow the setup flow outlined in this support article if you are new to setting up a sync.
To start, navigate to a grid view of the information you are wanting to enable syncing and click Share and sync and click Sync data to another base. We cover this and other limitations below. At this time, targets with two-way sync turned on are only able to edit records created in the sync source. It’s only possible to add new records in a source base. Changes made in a target will first sync back to the source before pushing to other targets upon the next sync. The lighter grey and dotted line arrows represent the indirect relationship between targets.The black two-sided arrows represent the direct connection between a source table and its target(s).There are two overarching concepts worth digesting before moving on: To illustrate how the two-way sync schema works consider the image below. Edits made in one or more target tables or interfaces in other bases will sync back to the source table. Understanding Two-way syncĪ two-way sync will always have a single source table where the initial sync share view is created. Interfaces in targets can be set up to permit edits that will sync back to the source. An indirect relationship with other targets is also established when setting up a two-way sync. Target - A table that has been set up to sync with the source.You can think of this as the master dataset. Source - A single-source-of-truth dataset that is synced elsewhere in Airtable.Sync permissions- General information about how permissions relate to Airtable Sync.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 overview - For more information on general feature behavior and plan limits.
TWILIO AIRTABLE INTEGRATIONS ANDROID
Platform(s) Web/Browser, Mac app, Windows App, and the Airtable iOS and Android mobile apps Related reading Additionally, editors can manually run syncs in the target base(s) to which they have access. Editors - Edit records in source or target bases that they have access to as base or workspace collaborators.Owners/ Creators - Can create, modify, delete, and run syncs in the base(s) they have access to.Introduction Plan availability Enterprise workspaces only Permissions Using two-way sync helps to prevent data silos and other inefficiencies in today’s hybrid work environment.
This article covers configuring an ecosystem of bases and interfaces so multiple teams can have the most up-to-date information.
Two-way sync allows existing records to be edited in one or more targets and synced back to a single-source-of-truth table.
0 kommentar(er)
