Hello, I'm curious whether anyone knows a workaround and/or why Esri chose to enforce the following limitation to trace networks.
Here's the situation/context: A person on our team created 3 trace networks, to be used along with other layers in 3 feature services. This person published those feature services. Later, we discovered that the Pro project for 1 of the feature services had used the wrong layer ID's. I open the project used to publish the feature service (and which contains the trace network), update the layer IDs, and try to re-publish the service.
At this point, I get the following error: Error 00265: Publishing user, <my username>, is not the trace network creator user, <other person's username>.
I'm sorry Esri, but can you please explain why this limitation exists? From what I can tell, the only recourse if the initial creator is no longer available is to completely remove the trace networks, re-create them, re-enable topology, then re-publish the service... every time the creator is no longer available?
As far as I can tell, the only possible solution would be a generic, shared user account that multiple people have the password/access to in Portal and which has the trace network licensing. That way, the trace network can be created with that account. Was that the intention? Is that the only real workaround?
