As a Shared Builder, I want to create two names for a field: one that is useful to me as a builder, and another that will be used in all page views.
This will prevent me from having to edit each view that uses that field, thus improving the speed of my app-building and editing workflow.
Would love to have this feature as well
I would like to second this! Right now the choice is creating a great user experience and manually mapping each column, or creating a great update experience and having confusing field labels for the user.
Hi Dagmar - We can also see how this would be useful! We've added it to our list for consideration.
We have implemented a feature in the new builder that allows you to add a field description to provide Builders with context about the field. Hope this helps you out enough here!