There’s actually is a pathway to creating the desired outcome, but you might not like it. Here’s how I did it once.
- If you’re into API development anyway, this approach should be well within your wheelhouse; my approached leaned on Google Apps Script long before script automation and script blocks existed, but it could be NodeJS or even script actions.
- Imagine a dedicated [empty] table that matches the desired format of the table you want to build dynamic view results.
- Now imagine an API process that listens for calls from Airtable that include filter specifications that are dynamic. For example, a button that calls your dynamic “view builder” or a script block that prompts for the filtering requirements.
- The view builder (API process) simply transforms the filtering criteria into a collection of records that are pushed back into the empty view table.
- User wants a different view? Prompt [again] for the filtering criteria; instantiate the new data set.
There are many reasons this is a terrible approach; it is a kludge without question, but it does provide a way for non-technical users to create new views of their data dynamically.