My Idea: Move attribute table formatting to be within a map and not the data source.
Currently, if there are multiple maps in a single project that tie to a common data source in Pro, changing the attribute field mapping in one map results the attribute field mapping in other maps being changed as well.
I handle the addressing for the County I work in and am currently involved drilling into properties with subaddressing (trailer parks, apartments, ...) for 911 purposes. To work effectively on this specific task I created a new map and changed the attribute table field view to present a very narrow selection of fields for the address point. My main map in the project needs to retain the full field configuration for regular business inquiries.
Unfortunately Pro appears to tie the attribute table field mapping to the data source and not the map so either the main map or the work task map ends up misconfigured and inefficient for data management.
One of the early discussed benefits of Pro being the replacement for ArcMap was the availability of multiple maps in a single application. If the attribute table of a feature class cannot be configured differently across multiple maps in a single project I have no other option other than to run multiple instances of Pro like I did with ArcMap.
Regards,
Tom