Select to view content in your preferred language

Unexpected field alias behavior when renaming field via Fields View

468
1
Jump to solution
06-09-2023 07:02 AM
Labels (1)
Bud
by
Esteemed Contributor

ArcGIS Pro 3.1.2; mobile geodatabase standalone table

In the Fields View, if I rename a field, the field's previous name gets used as the field alias.

Why is that happening?

Video:

0 Kudos
1 Solution

Accepted Solutions
Bud
by
Esteemed Contributor

Esri Case #03362627 - Unexpected field alias behavior when renaming field via Fields View

These are the steps to reproduce: 

  1. Create two mobile gdbs: mgdb1 and mgdb2
  2. In mgdb1, create a non-spatial table with a text field: T1.
  3. Copy the table to mgdb2.
  4. In the table in mgdb2, delete the field alias. Save.
  5. Rename the field from T1 to T2. Save.

Notes: 

  • The field alias for T1 in the table in mgdb1 does not need to be delete before copying.
  • The behavior only occurs if the table is copied from another mgdb. The behavior does not occur in the table in mgdb1.
  • The Field table must be opened by right-clicking on the table in the Catalog > Data Design > Fields. The issue is not reproducible if the Fields table is accessed by right-clicking on the table from the Contents. This is why I was not able to reproduce originally. Opening the Fields table from the Contents would be the workaround to use until the bug is fixed. 

BUG-000159633: In a mobile geodatabase table in ArcGIS Pro, the field alias gets automatically set to the previous field name.

View solution in original post

0 Kudos
1 Reply
Bud
by
Esteemed Contributor

Esri Case #03362627 - Unexpected field alias behavior when renaming field via Fields View

These are the steps to reproduce: 

  1. Create two mobile gdbs: mgdb1 and mgdb2
  2. In mgdb1, create a non-spatial table with a text field: T1.
  3. Copy the table to mgdb2.
  4. In the table in mgdb2, delete the field alias. Save.
  5. Rename the field from T1 to T2. Save.

Notes: 

  • The field alias for T1 in the table in mgdb1 does not need to be delete before copying.
  • The behavior only occurs if the table is copied from another mgdb. The behavior does not occur in the table in mgdb1.
  • The Field table must be opened by right-clicking on the table in the Catalog > Data Design > Fields. The issue is not reproducible if the Fields table is accessed by right-clicking on the table from the Contents. This is why I was not able to reproduce originally. Opening the Fields table from the Contents would be the workaround to use until the bug is fixed. 

BUG-000159633: In a mobile geodatabase table in ArcGIS Pro, the field alias gets automatically set to the previous field name.

0 Kudos