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

Allowing Interfaces to Use Non-Primary Fields as Header Text

Showing results for 
Search instead for 
Did you mean: 
5 - Automation Enthusiast
5 - Automation Enthusiast
Status: New Ideas
What is the proposed idea/solution?

It often makes sense to use a unique id field as the primary field in a database (for example "customer_id"), especially as linking records requires the primary field to be used. When this data is then displayed within an Interface, many of the interface elements will show the primary field in bold at the top of the record, when most end users would wish to see the customer name for example. 

How does is solve the user problems?

Interfaces would be far more clear if records could be displayed with more control over if or how the primary field is displayed, allowing databases to reserve the primary field for unique data strings.

How was this validated?


Who is the target audience?

Interface users.