Setting to disable field aliases

5130
16
11-05-2021 07:45 AM
Status: Open
Labels (1)
MarianneCardwell
Occasional Contributor

Add a setting to Pro (under "Table") to show field names instead of field aliases by default. It's tedious to change it manually for each table.

16 Comments
Matt-Goodman

+1

When I'm browsing tables in the Catalog view, I'd like to be able to browse through the actual field names within all the tables I'm skimming through. I understand that I can mouse-hover over any given field to see the actual name, but this isn't practical when trying to skim through big schemas. Being able to set a user's system default (either to alias, or actual) would be highly beneficial. 

CarlAlbury

+1

Like others, I would much rather have the actual field name be the default display in all situations. 

SteveMac

Please add this has a default option in Pro settings. As others have mentioned, when browsing LOTS of tables in Catalog View, it would be nice to have the actual field names default (and not have to hover over every field...). Seems like a very small change, so please add! 🙂

SavannahRoybal

This drives me insane every time I need to join datasets. Please fix this 🙏

paulaedwards2

Did I miss the fix?  I'm in Pro 3.5 and still don't see a way to toggle off the aliases.  I don't want to have to go in and remove over 100+ aliases individually.  We have to keep the data we're working in a specific data model and don't want to remove anything from the customer's original data model.  But I need to see the actual feature names in gdb in my content pane, not the aliases.  I'd also prefer the attribute tables to only show field names by default and if you want aliases you can select that option.  Is there a setting I can change in the project's options?

MatthewSackrison

In addition to all the excellent points already made here in the comments, if you do go through the laborious process of switching it manually on each of your layers, those settings do not save to either .lyrx or .mapx files, which means you need to use an .aprx as a template if you want to maintain that. With no Production Views (equivalency request for that to be added to Pro was rejected because "you can use Maps to symbolize the same data differently") this means any alternative symbology sets you want to maintain these in settings in need to be also stored as Maps within an aprx. With the number of layers we work with the more Maps you've opened in an .aprx the slower Pro runs and the more likely it seems to stop showing edit changes to the geometry until you wipe the display cache.