List Field Dependencies


#1

Have you ever found yourself asking these questions?

“Why did I create this field?”
“Why do have a ‘Name - Status’ formula in this field?”
“Can I delete this field?”
"What’ll break if I delete this field?

It’d be nice if we could see where our fields are being used. Perhaps a third tab in the “Customize Field Tab” area, right next to “Formatting.” Where it would list dependent fields!

BOOM. DO IT! :slight_smile:


#2

This is why field descriptions (as opposed to field names) offer a place to put important documentation of what the field is for and why, etc. Airtable is likely trying to favour simplicity over complexity while being able to have many collaborators.


#3

Simplicity is precisely why I suggested the feature. It’d just make the product stronger. Airtable is a differentiator. They set themselves apart from traditional relational databases. If I wanted to go the route of full DB design a la ERD’s or UML, I would just go back to SQL. Freeform text is never preferred anyways. It relies on human intervention and maintenance.


#4

I might suggest a distinction between INPUT/EDITOR fields and SYSTEM/CREATOR fields. Agreed, we have a TON of formula fields that should be invisible to virtually all users (save for Creators). They confuse INPUT/EDITOR users, and would ideally be hidden nearly across the board. Obviously we hid such fields in INPUT/EDITOR views, but it’d be better to simply LOCK THEM DOWN.