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; } } }

How do I bulk update a branch versioned feature class without triggering editor tracking attributes

DrewDowling

We have a feature class that is part of a parcel fabric. The feature class is branch versioned and published through a feature service.

I need to do a bulk update on all features and don't wish to trigger the editor tracking attributes. In ArcMap I was able to do this by doing a field calc outside of an edit session. Is there an equivalent way of doing this in Pro with branch versioned data?

Find more posts tagged with

Geodatabase

Desktop

Feature Services

Accepted answers

All comments

DrewDowling

Good luck. I'd like to know what Tech Support suggest.

In my case the combination of direct connection and disabling topology speeds up bulk updates by hours.

Do you have any attribute rules in place? They can slow things down as well.

ArizonaGIS

Thanks @DrewDowling running a field calc right now with your suggestion, and it is still painfully slow. Time to reach out to Esri Tech Support to see if my branch versioning architecture is correct. Thanks again. - Eric

DrewDowling

@ArizonaGIS

If you are referring to the original question of doing bulk updates without triggering editor trackling? No I never figured out how to do this with Pro.

If you are talking about performance problems then the quickest way to bulk update I found is to make a direct database connection using the SDE user (or whoever is the owner of the Default version) and then use geoprocessing tools.

In pro add the feature class to your map through a direct database connection as the SDE user. Then use geoprecessing tools or field calculator to do an update. Depending on what you are doing you might want to disable topology as well.

ArizonaGIS

@DrewDowling, @Andrew_McClary, @RiccardoKlinger & @LanceCole did you figure out a solution? I am attempting to do edits on a feature service that is part of a branch versioning dataset. I am running a field calculation of 200K records to update one field to populate the values to Null, and the calculation is incredibly slow, almost to the point it doesn't seem to be writing to the service.

DrewDowling

@Andrew_McClary, @RiccardoKlinger

I never figured out a way to do this with the Pro client.

I was able to do it using SQL. The only issue I noticed was that the version difference comparison tool stopped working. This is the tool in the Pro versioning ribbon that lets you see differences between versions. I don't know for sure if the SQL edit broke the tool, it is only a guess.

If I created a new feature service with a different name then the version difference tool worked again.

@RiccardoKlingerI get slow performance on a large number of edits as well using feature services. In my case it was the topology. I had better success in bulk updates by disabling topology first and then doing the edit.

DrewDowling

I played around with your suggestion of using different combinations of cursors and field calculate both inside and outside an edit session and every time the update worked the editor tracking also got triggered. I was using direct database connects and not the feature service.

So looks like I'll have to figure out another method, probably use the non esri approved direct SQL.

Thanks for your help Lance.

LanceCole

I can understand your reservation.

I had recommended using an Edit Session in python to perform your bulk update. We use this regularly to update attributes in our versioned databases without modifying the editor tracking attributes. However, I noted you are using a "branch version," which must be edited via a feature service. Not sure how that plays into editing data without updating the editor tracking attributes. I have been avoiding going down that path.

DrewDowling

I really don't want to go down the path of disabling editor tracking or unregistering the versioning. I went through this before back in the arcmap days and I found it very messy, especially when the feature class was part of a complex dataset like Fabric or Network.

LanceCole

Did you try and disable editor tracking before performing the bulk update then enable tracking again?

Enable or disable editor tracking

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.