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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |