Hi, I have asked a question about topology in the UN but may have put it in the wrong category to get the correct views. I would appreciate any help or insight as to why the Enable Topology tool is not recognizing my dataset is versioned, even though it is definitely versioned.
Solved! Go to Solution.
I had the same issue. Initially, I simply right-clicked the dataset > Manage > checked Versioning, but that didn’t work. I then ran the 'Register as Versioned' tool for the dataset, which solved the issue.
Are you enabling client-server (ie, referencing it via .sde)? If so, make sure your workspace is set to branch:
If you are enabling via services (ie, http://), did you publish with Version Management?
Hi Paul, yes my workspace is set to branch. Here is a screenshot you can check
Can we enable it through the portal connection? I feel like I have tried that in the past and I get a spatial index error.
If you are enabling via services (ie, http://), did you publish with Version Management?
In response to this, yes we did do that, although I am trying to enable via the SDE connection.
Ok, let's focus on the client-server enabling then.
When you ran "Register as Versioned", what did you input?
Typically i just right click on the UN feature data set in the catalog window, then select Register as Versioned. I have never actually run a tool.
When you ran "Register as Versioned", what did you input?
I did just check the admin connection (shown in the screenshot), even though I have not tried to enable topology on that connection, I have not registered the un_admin connection as versioned it seems. They are both pointing at the same enterprise dbase, however I really only use the owner connection (which is just an role I created in the enterprise dbase under the admin connection).
It's probably best to hop on a call so we're both on the same page. Shoot pleblanc@esri.com an email and let's go from there.
Any Update?? Im getting similar issue