Ref columns as label in AppSheet DataBase

[Gustavo_Eduardo]

What is the purpose of having an ID in a database (among other things) if it isn’t used to access data in other tables?

AppSheet has taken on a significant challenge with the "AppSheet Database" (a task that, in my opinion, might not be their priority—but who am I to say?). While the idea is promising, it seems to receive less attention than other parts of the platform.

AppSheet requires a Label field to be mandatory in any database. I find this excellent because it saves time and prevents inconsistencies. However, when working with Google Sheets, it is possible to use Ref fields as Labels. This is fantastic because, in these cases, we’re not pointing directly to the Label but to an ID that in turn references another Label.

So, what’s the advantage? If I choose a Ref field as the Label in one table, any update to the Label in the referenced table is automatically reflected in all related columns in other tables. Unfortunately, this is not possible in the AppSheet Database, as it doesn’t allow using Ref fields as Labels. Instead, you must create a dedicated field and update it manually or through bots, which is unnecessarily cumbersome (basically like scratching your left ear with your right hand—pardon the humor).

Please allow Ref fields to be used as Labels in the AppSheet Database. This would significantly simplify the design and maintenance of applications, aligning better with common relational database practices.

[Lizat]

I agree. And since it's possible elsewhere in the suite it makes sense to have it here as well.

I have several applications where my data is 'divided into specific groups of data needed by a given sort of user. They don't need everything and to avoid everything becoming too cumbersome I have several tables with data all relating to the same items but usually used discretely