In the legacy version of the platform, it is possible to provide a simplified view of your datasets (by hiding or reordering fields).
However, these adjustments are purely visual: hidden fields remain accessible via exports and APIs, which can lead to confusion.
📆 August 31: full deprecation of table view configuration
The table view configuration will be deprecated (whether you are using the legacy or the new platform experience). The table view will automatically reflect your dataset schema (same fields, same field order). As a result, explored, exported, and queried data will be fully consistent. ✅
📆 June 23: switch to ‘read-only’ mode for the current configuration (intermediate step)
You will no longer be able to edit it, but it will remain visible in your back office as a reference (the change will take full effect on August 31).
👉 Preview of your back office on June 23, depending on your setup:
Case #1 - you are on the legacy experience (or have only migrated your back office to the new experience):
Case #2 - you are on the new experience (back office and front office):
3 ways to keep providing simplified views 🚀
1. Update your schema: align it with your current table view (reordering or removing fields)
2. Configure the dataset “Security” tab: define field visibility based on users or groups
3. Create custom views (new experience only): design table views with filtered, sorted, or limited columns. The full schema-based view remains available, but you choose which one to highlight
Need more information?
Check out the documentation.