nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Validate doesn't validate "Error" dirty areas.

EdX1

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.

Najděte více příspěvků označených jako

Accepted answers

All comments

LexAdove

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

RobertKrisher

@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.

GISUser1619_Nguyen

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.

1.JPG

2.JPG

LexAdove

Fixing Duplicated Vertices on the Structure Line.

Notice the smaller dirty area inside? It's another Structure Line (new guid) with the same duplicated vertex on the same coordinate as the other structure line.

LexAdove

The number of vertices increases when trying to fix a duplicate vertex/ dirty area issue (Communications Line)

LexAdove

Any update on this? This is really getting frustrating.

It seems this error has been here for a while. Every time I fix the same issue like yours, my UN creates new vertices, creating duplicates and more dirty areas to fix. It's really never-ending.

I've submitted a bug that took almost a year. This is for editing vertices of a fibre cable with duplicated vertices. It just freezes right after hitting Edit Vertices and you will be left with summoning Task Manager to kill ArcPro.
https://support.esri.com/en-us/bug/BUG-000179744

Another one I noticed is when your fibre cable has dirty area linked to structure line (segments) these structure lines will also have a dirty area with an erorr code = 0 that does not disappear unless the error on fibre cable has been fixed.

ELIZABETH50

Hello,

Was the issue resolved?, I noticed the same issues now with Pro 3.2 and Utility Network Version 6. I get the no dirty area found during validate window.

PhilLarkin1

@EC1 Did you submit a tech support ticket and did you come to a resolution or bug report?

EdX1

ArcPro 2.7.1, how do I find my UN version? I think I am using UNtools 2.7.

EdX1

In this case zooming/validating without me editing it results in 'no dirty areas found', as you can see in the first picture. Its quite annoying!

Anonymous User

I often have the issue where I validate and the dirty area doesn't go away. To resolve this, I open the attribute table, zoom to one of the dirty areas, and validate. Sometimes I have to do this one by one, or sometimes I do a couple and then zoom out and can get the rest to validate together.

AnthonyRyanEQL

Raise this issue through Esri Inc Support. We are having similar issues and working with Esri Inc UN dev team to solve. What's version of UNM & Enterprise are you on. I'm currently using ArcGIS Pro V2.7.4 with ArcGIS Enterprise 10.8.1 with UN Patch 6 using UNM V3.

Good luck

Připojte se k diskusi

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.