Hi all,
Perhaps there is an error in the feature renaming logic of Pro. I have observed this in both 3.0 and 2.9.3 but don't have a machine to look further back.
During some data management I had to rename some features in a file gdb.
I accidentally inserted a space 'feature 988' instead of an underscore 'feature_988' with some additional characters in the feature name and both Pro 3.0 and 2.9.3 return the obvious error with no visible change in the feature name. However once I closed the error dialog I went to rename the feature again and with the rename feature active the ' 988' was visible.
Perhaps 2 things need to occur here:
- The renaming logic needs to be looked at - a first level check for feature rename validity that errors out of the effort before the rename actually kick off.
- The original name needs to be retained so if in the event of an error the feature name is not left in a potentially weird situation like I am seeing.
Respectfully,
Tom
