Select to view content in your preferred language

Batch Update Field Aliases from CSV in the Fields View

153
0
03-24-2026 11:55 AM
Status: Open
Labels (1)
JoshMakesMaps
Regular Contributor

What:

Add a built-in option in the ArcGIS Pro Fields view to import/export field aliases from a CSV file (field name + alias columns).

Why:

Many datasets — especially those sourced from enterprise systems, assessor databases, or MapServer services — have dozens or hundreds of cryptically named fields (e.g., SITUS_POST_DIR, ASR_IMPR, NUCLEUS_ZONE_CD). Setting readable aliases on these is essential for usability in pop-ups, dashboards, and attribute tables, but the current workflow requires editing each alias individually in the Fields view.

Current workarounds and their limitations:

- Manual editing — works but is impractical for 50+ fields. Error-prone and tedious.

- AlterField (arcpy) — only works when the source data is editable. Fails on read-only sources like MapServer layers, feature services, and enterprise geodatabases where the user lacks schema permissions.

- CIM access via Python — works but has an undocumented prerequisite: for MapServer layers, at least one alias must be manually set through the UI before the CIM exposes the correct field description objects. Without this step, the CIM contains a disconnected set of field entries that setDefinition updates silently without effect.

Proposed feature:

In the Fields view, add an Import Aliases button (or right-click option) that accepts a two-column CSV:

field_name,alias
APN,Assessor Parcel Number
FRACTINT,Fractional Interest
OWN_ADDR1,Owner Address Line 1



And an Export Aliases button to generate the CSV from current values — making it easy to prepare, review, and share alias mappings across teams and projects.

This would work at the layer level (not requiring source schema access), just like manually editing aliases in the Fields view today.

Who benefits:

- GIS analysts working with published services they don't administer.
- Teams standardizing field aliases across multiple maps and projects.
- Anyone working with assessor parcels, census data, utility asset tables, or other schemas with abbreviated field names.

This feels like a natural extension of the Fields view that would save a lot of time and reduce the need for Python workarounds.