Hi everyone,
I'm trying to change the alias of a feature class, but after I type it out and hit "OK," it only saves one additional letter. For example, I have a line feature class called "ALD." I'm trying to update the alias from what I originally had ("Anoxic Limestone Drain") to "Anoxic limestone drain" to match the capitalization of the other feature classes in this geodatabase. When I delete the current alias and type out "Anoxic limestone drain," the first time it'll save the alias as just "A." Then when I do it a second time, it'll save the alias as "An." Third time: "Ano."
I'm doing this from the catalog view by right-clicking on the feature class and selecting "Properties," then renaming it in the Alias field under the Source tab. If there's a better way to do this, please let me know. I would really like to avoid remaking this entire geodatabase just because a handful of the original aliases were capitalized inconsistently...
Solved! Go to Solution.
This issue was identified in earlier versions of 3.3.x and has been fixed in later releases (https://support.esri.com/en-us/bug/BUG-000168443). Please consider upgrading to version 3.3.4/5 or 3.4.
This might be relevant at least for a file geodatabase.
When attempting to modify a feature class alias after being upgraded to ArcGIS Pro 3.3, I now experience the same exact behavior @TrentonWalker described. Has anyone reported this to Esri technical support as a bug?
I also experienced this same bug as described on 3.3.1.
A workaround that I found was to paste in the new alias from another text box. In my case, I used a web browser search bar.
No idea what's causing the bug or if this workaround is 100% reliable, but hopefully this works for anyone else who encounters the issue before they fix it.
I'm on Pro 3.3.1 and I'm experiencing this. Changes to the alias are very buggy. I'm seeing the one letter at a time, but also I'm unable to delete the final letter and I'm stuck with an alias of "D".
This issue was identified in earlier versions of 3.3.x and has been fixed in later releases (https://support.esri.com/en-us/bug/BUG-000168443). Please consider upgrading to version 3.3.4/5 or 3.4.