nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Check Geometry tool on a Versioned Feature Class

TimJohnston3

Why is it not possible to use the Check Geometry geoprocessing tool on a Versioned Feature Class?

ERROR 001259: Operation not supported on a versioned table.

I suspect I have invalid geometry in my Versioned Feature Class. Is there a way to check geometry besides exporting the data or unversioning the table?

If I have a separate geoprocessing script which reads from this Versioned Feature Class which contains invalid geometry then my script will fail. Does that mean I should not write geoprocessing scripts against Versioned Feature classes because they may contain invalid geometry and my script could fail?

Find more posts tagged with

Accepted answers

All comments

David_Brooks

@TimJohnston3 , just out of interest. Can the Repair Geometry tool run on a versioned FC? If so, maybe you just repair straight off the bat. Then have the option to reject the reparations if you didnt want them repairing?

se2539

Ran into this same issues today; went to check geometry on all of our organizations SDE feature classes via python script and received the same error. From what I'm seeing there is no way to directly run check geometry unless you unversion each feature class (which is cumbersome) or if you have a backup, say with a replica, run the tool against that. I plan on going the latter route as we keep daily replicas of the entire database.

DanMallett

Can you add this to Ideas?

DanMallett

@Thomas_Bennett created an Idea already -> go give it Kudo's!

https://community.esri.com/t5/arcgis-pro-ideas/check-repair-geometry-tool-should-be-able-to-run/idi-p/1133213/jump-to/first-unread-message

Kevin_MacLeod

Because 3D digital twin is more important. This is a crucial functionality gap. Versioning in general, is really woolly, and needs some serious improvement. (Ability to compare child to child, pick edits to approve/reject/modify; manually or in batch by sql/spatial query, like Conflict Pane but scaled up; the list goes on.)

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.