Topology in a Versioned GDB

JoeBorgione — Thu, 11 Oct 2018 14:12:13 GMT

For the past few weeks I've been in knock down, drag 'em out, bloody knuckles fist fight with a versioned geodatabase and a topology there in (see Export Topology Errors and Versioning , Reconcile & Post hangs , Topology Validation versus Fixing the Actual Error(s) , Permissions to Validate Topology ...)

The latest skirmish is about to start: I'd like to try an validate the topology using a stand-alone arcpy script, and have a question about that approach.

Topology and versioned geodatabases—Help | ArcGIS Desktop , explains the method to create a topology in a versioned gdb: basically, create a feature dataset, add your feature classes, create your topology and the register the feature dataset as versioned.

Validate Topology—Help | ArcGIS Desktop explains how to use the ValidateToplogy_managment() method and states:

If you validate an enterprise topology in ArcCatalog, the feature dataset that the topology is within be registered as versioned.

I take this to mean if I were to run the Validate Topology gp tool from an ArcCatalog session, I first need to unregister the feature dataset as versioned.

Bottom line: If I run ValidateToplogy_managment() as part of a standalone script, do I need to unregister the feature dataset as versioned prior to validation?

Re: Topology in a Versioned GDB

JoeBorgione — Thu, 11 Oct 2018 15:24:32 GMT

After a test or two, it appears that you do not have to unregister the feature dataset as versioned when using a standalone arcpy approach.

topic Topology in a Versioned GDB in Geodatabase Questions

Topology in a Versioned GDB

Re: Topology in a Versioned GDB