
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎Jan 27, 2025 01:14 PM
Why do we use the Data Set feature? What is the point / benefit? If the data set is fed from one table in a base, then why can't we simply sync this table out to other bases in a workspace?
The guide doesn't clear this matter up in my opinion.
https://support.airtable.com/docs/data-sets-and-verifying-data-in-airtable
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎Jan 27, 2025 06:21 PM
I do like the way it's easy to add a data set from the data library vs needing to get the shared link / set the base, table, view, and can see how that might be better for elss technically inclined folks

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎Feb 03, 2025 11:13 PM
In my usage of source data, it is shared to different bases, then certain data is hidden from view and the sorting is altered depending upon which base is using it and for what purpose.
Once the share is there and you import the table into the base, you never need to look for it again. So I'm not sure it saves anything. If you were constantly having to manually go look for data then possibly yes, it could save time.
I'm probably not using airtable in the structure it is intended for, but it is the central hub to our company with 3 bases referring to each other constantly, and 4 other bases with say a lookup of people names and some of their details.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎Feb 14, 2025 04:18 PM
I'm also confused about what the benefits are and hopeful someone can explain! We have a base that serves as the source of truth for a CRM and then several other bases that rely on that data and some that supplement that data. Other bases and fields operate totally independently of the CRM.
Currently the source of truth lives in one place and gets synced elsewhere. I can only see two benefits of switching to a dataset:
- Permissions (though I'm not sure why syncing particular views wouldn't do this)
- Making the source of truth visible in the data library (though I'm not sure why users would think to look there instead of the CRM base that they all use)
Does anyone else have some insight into this? It feels like something we could leverage, if I understood why. For example, if one base adds a field to the primary dataset in their base, is that usable/visible to other bases who rely on the dataset?
