I have a feature class inside of a feature dataset with the cannot overlap and cannot have gaps rules attached to them. The error inspector/validation works just fine, but when I try to apply the suggested fix, nothing happens. I am clicking on the fix error validation tool, then click on the red line where the error is and then select remove overlap from the pop up box. Nothing happens. When I run validation again, the error remains. I am on Pro v3.3.1.
Does anyone know what I am doing wrong?
I also cannot get the map topology align edges tool to recognize the dataset so I can do it manually.
I can't edit my original post anymore, but I should have included that the feature dataset is in an enterprise gdb.
@michel When you click 'remove overlap' and before you validate topology the second time, does the error record disappear from the Error Inspector table?
Do you have any other topology rules applied on the line feature class? It is possible for different rules (such as 'Must Not Overlap With(Line-Line)' or 'Must Not Self Overlap') to result in similar but separate errors at the same location that must also be fixed separately.
Hi @JMutunga
no the error record doesn't disappear from the table and I don't have any other rules applied. I just found out late yesterday that this seems to be an issue with enterprise gdb's of which a fix is supposedly coming when we upgrade our server to 11.x (can't recall what we are at or going to) next month. I guess I'll have to wait and see.
I did test it on a regular file gdb and it works as expected.
@Michele Thanks.
Just to confirm, is this issue occurring for overlapping polygons or overlapping lines?
@Michele and anyone else running into this issue, this is a known behavior currently under investigation by the Editing team.
@Michele If your data source is a feature service published to ArcGIS Enterprise 11.3 and editing in ArcGIS Pro 3.3.1 (or 3.4), then you will unfortunately be affected by this bug.
You can track the progress of this issue on the Technical Support website using this bug number: BUG-000173471.