Field mapping - mass entry of fields information like Fields view

[wayfaringrob]

Based on the numerous issues I've had with the newer field mapping view (and documented on this site), I hesitate to say it's an improvement over the old interface. One move I think it does well, though, is move toward a table-based interface:

It almost resembles the fields view, but it's less convenient than Fields view. In Fields, you get an overview of all fields and can easily edit. In field mapping--where the minutiae, I'd argue, matter more--you have to click one-by-one down the side, looking at each field individually. I understand that there are needs for different controls in field mapping, but if it could resemble the fields view in its structure by being more of a basic table, that would be useful.

[BruceHarold]

Rob can you share a link to the issues for the field map view?  Thanks.

[wayfaringrob]

Here are some (that I've authored) @BruceHarold 

Field mapping - only remove fields I remove. - Esri Community

Export features - do not export fields removed fro... - Esri Community

Spatial joins - allow user to remove ALL fields fr... - Esri Community

Allow easier typing in field properties - Esri Community

[BruceHarold]

Thank you Rob, I have shared internally.

[MargaretCrawford]

Just to comment on the original idea, for workflows that involve removing fields, renaming fields, or changing other field properties, a table view like that would work well. But we still need to consider other workflows that involve setting Source fields from multiple tables or calculating statistics. We can keep this idea on the table, but for future redesigns we want to be able to accommodate simple and complex workflows.