topic Re: Editing problem with Trace Network services in Trace Network Questions

Editing problem with Trace Network services

MarcoMattioli — Thu, 23 Apr 2026 13:28:50 GMT

Hi everyone,

I am implementing an environment based on ArcGIS Enterprise 11.5 and an Oracle. enterprise GDB I created a Utility Network that works fine, but I have not the same luck with Trace Networks.

I converted them from Geometry Networks without issues and then I published them in our Portal without errors or warnings.

But when I try to edit the feature service in ArcGIS Pro, the magic happens: when I create a feature, two feature with coincident geometries are created. The two features have different and not consequent OBJECTID but same attributes (GLOBALID included) and a single row in table (but if I select them, below the table ArcGIS Pro says "2 of ... selected").

If a point is created, you can delete the "phantom" -apparently- without consequences.

If a line is created, you can delete the "phantom", but the remaining feature cannot be modified. If you modify the geometry of one of the two lines, you can see that the network sees them as connected.

Anyway, ArcGIS Pro does not report any error. The ArcGIS Server logs also do not report any error or warning, so I don't know where to look.

Based on my tests I can say that:

- The anomaly appears to be related to Trace Network services. If you publish the same data without the Trace Network layer, you can edit them correctly

- Other layers in the Trace Network service that do not partecipate in the network are also affected

- Editing works fine in the Map Viewer embedded in Portal, probably because it ignores the Trace Network

- Everything works fine publishing the Trace Network service from a File GDB

- I also tried with the simplest possible Trace Network, without success

So, it seems that it's something related to the interaction between Trace Network services and Enterprise GDB (Oracle, maybe?), but I can't say anything more.

Can anyone point me in the right direction?

Thanks,

Marco

Re: Editing problem with Trace Network services

NathanGEOregon — Fri, 01 May 2026 14:41:46 GMT

I don't have any advice, other than to say this sounds like a bug and unfortunately will most likely require engaging with ESRI support. We are running a Trace Network on Enterprise 11.3 and Pro 3.3 and successfully editing without these types of issues.

Re: Editing problem with Trace Network services

MarcoMattioli — Mon, 04 May 2026 11:37:24 GMT

If you are at 3.3 then DON'T pass to 3.5. It appears that it is a bug (BUG-000179882 for ArcGIS Pro) that affects all the 3.5 releases, from 3.5 to 3.5.6.

Re: Editing problem with Trace Network services

NathanGEOregon — Mon, 04 May 2026 14:52:24 GMT

Thanks for the heads up! We planned to move to Enterprise 11.5 / Pro 3.5 this summer so we will need to do some testing with Pro 3.6 instead it sounds like.

Re: Editing problem with Trace Network services

MarcoMattioli — Mon, 04 May 2026 15:03:06 GMT

You are welcome! We tested with the 3.6 and the bug is indeed corrected. If you want, you can wait for the 3.7/12.1, given the longer support.