Weird issues when editing with custom .NET tools in Pro 3.2

BrianBulla — Wed, 26 Jun 2024 15:15:35 GMT

This might be related to this, but my workflow to create these "STATE" issues seems to be a bit different.

https://community.esri.com/t5/arcgis-pro-questions/arcgis-pro-3-2-drawing-alerts-returning-state-id/m-p/1349945#M75223

This is my workflow to generate the issue:

1. Add a new feature

2. Use a custom tool I have created that modifies some attributes of the selected feature from step #1.

3. Add the next new feature. At this point the feature is added, but just not visible on the display. If I pan the map around, all seems ok.

4. Save edits using the "Save" button on the edit tab. Again, all seems ok.

5. Pan the map again, and all sorts of "Drawing Errors" start showing up and features on the map start mysteriously (and randonly) dissapearing.

6. Close ArcPro and reopen.

7. When ArcPro opens, the feature created in step #3 is now visible.

Can anyone help to figure out what the heck is going on? It seems like the only time this happens is when I run one our custom .NET tools during the editing. These tools have all worked flawlessly for years, and recently I migrated them from 2.9 to 3.2 using the guides from esri. In most cases, no code was changed....I just had to run the "update references" and "migrate" tools.

Is anyone else seeing issues with custom editing tools in Pro 3.2??

Thanks,

topic Weird issues when editing with custom .NET tools in Pro 3.2 in ArcGIS Pro SDK Questions

Weird issues when editing with custom .NET tools in Pro 3.2