Trace Network Creator vs Publisher (error 00265)

[AndreLoerch]

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?

[AndreLoerch · Accepted solution]

I found a reasonable solution (I'll share it here just in case anyone else encounters this issue). 

While the language of the error message clearly says "creator" the reality is that it's the portal item owner that matters. 

1. Run the 'Update Portal Dataset Owner' GP tool
2. Select the trace network, and enter the desired new owner account
3. Republish the feature service (now there is no error about the creator being different from the user)

@Esri, the documentation here should be updated to provide this as a solution: https://pro.arcgis.com/en/pro-app/latest/help/sharing/analyzer-error-messages/00265-publishing-user-...

Also, the error should say "owner" and not "creator".

[JonDeRose]

@AndreLoerch 

The active portal user account as the owner of the dataset in portal and is based on the active portal user when the dataset is created. This owner allows you to restrict access for administrative tasks to be performed on on the dataset.   If the account used for your portal dataset owner has the potential to change it would be a good practice to create a headless user that your team would use for this purpose. 

As you noted in your solution above, we allow you to change this portal trace network owner assignment easily using the Update Portal Dataset Owner GP tool as long as you can connect to the dataset using the trace network dataset owner account.

Thank you for pointing out the issue with the documentation.  I will work with our team to make updates to this topic in a future release.

Jon