You can simply switch to Layout mode and rename field labels whatever you want them to be; or delete them completely. It has always been so. Or am I missing something in your query?
sorry, I forgot to mention, that in this case I just want to use a list layout like Excel.
If I have columns from different tables in this list view, then I have field names like
table_xyz::fieldname_xyz in my table_header, but just want to have a table header
like "ID" for example. And by now, if I export this data to Excel, I have these long
column names too.
alias names for fields generated as formulas would be a great idea for several reasons:
a) multilingual projects: You could have English language fieldnames and show a German, French or Dutch alias name in table view, sort, import and export dialogues
b) keeping fields out of sight: You often have a bunch of fields only for internal purposes. With an empty alias the user wouldn´t see them and wouldn´t be worried. Today he can see every field in sort, import, export, add field in table dialogues
c) handling short and long names: for building formulas and scripts short names are fine, but for the user longer descripting names would often help. The developer might understand n*v=g, but for the user net price * vat percent = gross price would be easier to understand
+ 1 ... yes that would be great
This would be highly useful. Keywords points out that field labels can be edited on layouts, of course, but there are so many places in FM where actual field names are exposed to the user (Export dialogs, to name just one such place), making a rigorous application of a naming system challenging. An alias or "label" that could be specified as part of the field definition (possibly calculated, per intex's suggestion) would facilitate hiding those cryptic naming systems from end users. As a bonus, then, the alias, rather than the developer's field name, would become the default label whenever a field is dragged onto a layout.
+111, would be so useful for table view and export.
It is too bad that field comments couldn't be used for this functionality (checkbox 'use field name or comment' in dialogs for export, sort, search and layout labels). The design function FieldComment() is utterly worthless as is anyway. :-)
But we've been asking for ability to alias for at least 7 years now so ...
One use of FieldComment is for tooltips.
At first I was thinking, "Why? What purpose would that serve?"
Then I went back to work on the solution I am redesigning. Now I'm angry that we don't already have that feature.
Plus several more.
Would help LOTS with customer facing bits of the solutions