<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>idea Batch Update Field Aliases from CSV in the Fields View in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/batch-update-field-aliases-from-csv-in-the-fields/idi-p/1692328</link>
    <description>&lt;P&gt;&lt;STRONG&gt;What:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Add a built-in option in the ArcGIS Pro Fields view to import/export field aliases from a CSV file (field name + alias columns).&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Why:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;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.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Current workarounds and their limitations:&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;- Manual editing — works but is impractical for 50+ fields. Error-prone and tedious.&lt;BR /&gt;&lt;BR /&gt;- 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.&lt;BR /&gt;&lt;BR /&gt;- 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.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Proposed feature:&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;In the Fields view, add an Import Aliases button (or right-click option) that accepts a two-column CSV:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;LI-CODE lang="c"&gt;field_name,alias
APN,Assessor Parcel Number
FRACTINT,Fractional Interest
OWN_ADDR1,Owner Address Line 1&lt;/LI-CODE&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;This would work at the layer level (not requiring source schema access), just like manually editing aliases in the Fields view today.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Who benefits:&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;- GIS analysts working with published services they don't administer.&lt;BR /&gt;- Teams standardizing field aliases across multiple maps and projects.&lt;BR /&gt;- Anyone working with assessor parcels, census data, utility asset tables, or other schemas with abbreviated field names.&lt;BR /&gt;&lt;BR /&gt;This feels like a natural extension of the Fields view that would save a lot of time and reduce the need for Python workarounds.&lt;/P&gt;</description>
    <pubDate>Fri, 27 Mar 2026 16:02:50 GMT</pubDate>
    <dc:creator>JoshMakesMaps</dc:creator>
    <dc:date>2026-03-27T16:02:50Z</dc:date>
    <item>
      <title>Batch Update Field Aliases from CSV in the Fields View</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/batch-update-field-aliases-from-csv-in-the-fields/idi-p/1692328</link>
      <description>&lt;P&gt;&lt;STRONG&gt;What:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Add a built-in option in the ArcGIS Pro Fields view to import/export field aliases from a CSV file (field name + alias columns).&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Why:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;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.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Current workarounds and their limitations:&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;- Manual editing — works but is impractical for 50+ fields. Error-prone and tedious.&lt;BR /&gt;&lt;BR /&gt;- 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.&lt;BR /&gt;&lt;BR /&gt;- 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.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Proposed feature:&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;In the Fields view, add an Import Aliases button (or right-click option) that accepts a two-column CSV:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;LI-CODE lang="c"&gt;field_name,alias
APN,Assessor Parcel Number
FRACTINT,Fractional Interest
OWN_ADDR1,Owner Address Line 1&lt;/LI-CODE&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;This would work at the layer level (not requiring source schema access), just like manually editing aliases in the Fields view today.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Who benefits:&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;- GIS analysts working with published services they don't administer.&lt;BR /&gt;- Teams standardizing field aliases across multiple maps and projects.&lt;BR /&gt;- Anyone working with assessor parcels, census data, utility asset tables, or other schemas with abbreviated field names.&lt;BR /&gt;&lt;BR /&gt;This feels like a natural extension of the Fields view that would save a lot of time and reduce the need for Python workarounds.&lt;/P&gt;</description>
      <pubDate>Fri, 27 Mar 2026 16:02:50 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/batch-update-field-aliases-from-csv-in-the-fields/idi-p/1692328</guid>
      <dc:creator>JoshMakesMaps</dc:creator>
      <dc:date>2026-03-27T16:02:50Z</dc:date>
    </item>
  </channel>
</rss>

