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:
Solved! Go to Solution.
Esri Case #03362627 - Unexpected field alias behavior when renaming field via Fields View
These are the steps to reproduce:
- Create two mobile gdbs: mgdb1 and mgdb2
- In mgdb1, create a non-spatial table with a text field: T1.
- Copy the table to mgdb2.
- In the table in mgdb2, delete the field alias. Save.
- 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.
Esri Case #03362627 - Unexpected field alias behavior when renaming field via Fields View
These are the steps to reproduce:
- Create two mobile gdbs: mgdb1 and mgdb2
- In mgdb1, create a non-spatial table with a text field: T1.
- Copy the table to mgdb2.
- In the table in mgdb2, delete the field alias. Save.
- 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.