idea Support the D(elete) in CRUD for Branch Versioning in Data Management Ideas

Support the D(elete) in CRUD for Branch Versioning

Anonymous User — Thu, 08 Dec 2022 00:12:13 GMT

I would like a simple way to delete obsolete rows from a branch versioned table/featureclass in the geodatabase.

Use case from here:

Say there's an organization that has policies prohibiting personal data in the geodatabase. Suppose, by accident, a social security number makes its way into the Customers table. The Manager tells the GIS admin "delete that immediately!"

If the geodatabase is branch versioned, how would the GIS Admin delete the row, or even just update the column in the "old" row?

Re: Support the D(elete) in CRUD for Branch Versioning

SSWoodward — Fri, 07 May 2021 14:08:56 GMT

Re: Support the D(elete) in CRUD for Branch Versioning

SSWoodward — Mon, 28 Mar 2022 19:46:13 GMT

Re: Support the D(elete) in CRUD for Branch Versioning - Status changed to: Under Consideration

SSWoodward — Thu, 13 Oct 2022 20:24:51 GMT

Re: Support the D(elete) in CRUD for Branch Versioning - Status changed to: Open

SSWoodward — Fri, 20 Jan 2023 01:44:25 GMT

Thank you for the Idea and comments.

As this Idea developed it became clear there were two discrete ideas being discussed. The first is the original idea which focuses on the ability to remove an individual, obsolete record from the archive tables of branch versioned data. The second focused on branch versioned archives growing continuously, and affecting performance over time.

This second focus is currently under consideration, but the work being considered would not meet the needs of the original idea. To more accurately reflect this, the comments pertaining to it have been moved to an idea specific to it.

Link - Trim Archive History Tool for Branch Versioned Data