Hello,
I am setting up a Utility Network Model.
I am using FME to push data into the model via a web feature layer. In this circumstance there were originally errors (small dirty areas) along the blue line, which were fixed via inserting required features to meet network topology rules.
When the smaller dirty areas were initially flagged, the selected line was also flagged. Now the other errors have been fixed, this blue line should not be flagged as an error anymore, as the issues have been fixed. But even when trying to validate the UNM thinks there is nothing wrong and does nothing:.
To fix this issue I am currently doing this, which is a very tedious and slow process:
I edit the vertices on the point with the red arrow, simply by clicking, draging and putting it back to its original position, after that the error area is now a dirty area:
and now it can be validated.
This seems to be a major bug in the utility network model. This issue is chewing up a large portion of users time to fix.
Is there a way to do this quicker? I have tried turning network topology off/on, refreshing the connection and restarting arcpro. The errors remain as the Utility Network Model validate does not seem to realise they exist until I manually edit and refresh that dirty area.
Please help, or fix this bug.
Thanks.
Yes, I got same issue when run " Validate current extent", It will happen if you not zoom out to cover "Dirty area extent" you want to validate. And can not fix by validate again, I must edit that feature again to update this dirty area and validate again.
It really make our customer confuse.
@GISUser1619_Nguyen There is at least one bug associated with the partial clipping behavior, I recommend you reach out to support to see if it resolves the issue.
Do you already have a Python script that can run in the background (nightly process) to validate these, or a task that you can run right after your FME to run the network validation :).
However, regarding the "validate not validating" - I have encountered that as well: it says Error Code = 0, but the validation fails and still has the dirty areas on. At first, I thought these were non-spatial-related tables, but after a few days/weeks, some Error Code = 0 that were last edited way back in 2021~2025 have slowly crawled back into the network. I now have 18k of these old Error Code = 0 (not actually an error since they have been cleared out previously on a full network validation - we've had multiple GIS updates since 2021)
So many bugs in ArcGIS Pro. I've spent almost 11 months trying to submit a bug ticket last year (Vertex editing bug). I don't want to do it again