When editing cells sequentially in a Shapefile table, ArcGIS Pro will begin to fail to correctly recognize what should be entered in the cell. It will fail to recognize keystrokes, leave characters behind from the previous cell value, enter characters out of order, and will even jump to other cells in the same column (usually previous cells). This behaviour also occurs when editing in the attributes pane when you are hitting enter to get to the next field then start typing.
Steps to create the issue:
1. Load a Shapefile (and optionally another layer or layers) into an ArcGIS Pro(2.6.x) map.
2. Turn on labels for any of the layers and zoom the map so a certain number of labels are visible(perhaps as few as 20 but this may depend on your computer's speed, how many layers you have, how many have labels turned on, perhaps even the number of characters in the labels, etc.)
3. Open the attribute table of the Shapefile.
4. Begin editing by typing in a cell then hitting enter to get to the next record and do that repeatedly without pausing for more that a second or two between hitting enter and beginning to type in the next cell.
(Or, select a feature and open the attributes pane and begin editing fields by typing then hitting then typing, etc. to edit multiple fields for the record. This assumes of course that there are at least several fields in the table.)
This issue occurs with ArcGIS Pro 2.6.x (I am currently at 2.6.2 but began noticing this issue at least at 2.6.0). It has likely been present since the ability to edit in this way was added. (This functionality was requested in an idea in 2017 by Nicholas McNamara.) Also see Rich Emerson's idea which seems related ("Do not refresh screen if editing an attribute not connected to display properties")
My system info, in case it is pertinent: Windows 10 Pro, 16GB memory; 64-bit; Intel(R) Core(TM) i7-7500U CPU @ 2.7GHz 2.90GHz
The workarounds for this issue are pretty simple: just turn off labels or pause drawing while editing. However, it is annoying and you can end up with weird values in your data if you don't immediately notice it's happening. (Thankfully I don't generally work with important dollar figures or planning measurements.)
This is more of a bug than an idea but Esri support recommended I post it here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.