This Product Ideas board is currently undergoing updates, but please continue to submit your ideas.

Ability to see which fields and views rely on a given field

Showing results for 
Search instead for 
Did you mean: 
6 - Interface Innovator
6 - Interface Innovator

It would be amazing to be able to see which fields and views rely on a given field (via linkages, formulas, and filters). Currently when we want to change a field’s type, format, values, or delete the field altogether, we are blind to which other fields or views will be impacted by that change.

To help address this for our bases, we have built a separate metadata base to visually map all the metadata of our other bases. We have a nightly process that crawls the schema of our bases and builds out a map of all Bases, Tables, Fields and Views, including which fields directly rely on other fields. Now, whenever we make a change to a field, we always check the metadata base to understand what other fields and parts of the system will be impacted, so we can ensure there are no hidden breakages and the base continues to work as expected.

6 - Interface Innovator
6 - Interface Innovator

This is an awesome idea! Have to put some though into how the dependents would be presented, but I’ve dragging a lot of junk around because I don’t remember if it affects anything important…

7 - App Architect
7 - App Architect

YES. A big +1 to this idea.

I’ve been using Airtable for almost two years now. I’ve learned A LOT and my base has grown A LOT. I’m now at the point where I know how to do things, especially with formula fields, much better and cleaner than when I started.

Some of my tables have over 100 fields and it has become very hard to keep track of which ones are still performing important functions and which fields were experiments that never panned out or that I improved on later. I want to start to “clean up” or “optimize” my base, removing and/or combining redundant fields.

I’d love to be able to look at field X and know that fields A, B, and C all rely on it; or, alternately, that no other fields rely on X and that, therefore, X can be deleted without causing unintended breakages elsewhere.

5 - Automation Enthusiast
5 - Automation Enthusiast

@Roman_Scher how did you do this?