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

Enable Editor Tracking

AndrewWharton

I am trying to enable editor tracking on datasets and am running into some problems. The simplest way to enable tracking is in the datasets under manage, but if I use that it automatically uses UTM for the dates which I don't want.

So instead I try properties on each feature class but with this method I have to create each field first that the data will populate into. With this method I can pick database time, though.

The third method is using the Enable Editor Tracking tool. The first problem with this is when I enter the version 10.1 dataset it causes an error saying the dataset is from an earlier version that doesn't support editor tracking. Then I try an individual feature class and it does allow me to select it without that error and enter my settings, but when I run the tool it fails saying I did not set any fields to store the edits in, but I checked the option to create fields if they don't exist.

Is there a solution to this? The only way that works gives me UTM time, but I don't want to be stuck with that. I am migrating data and would like editor tracking enabled first so that it will populate the fields for creation.

Trouver plus de publications taguées avec

Accepted answers

All comments

GregDreaper

FYSA. I just got burned by this jewel below, http://resources.arcgis.com/en/help/main/10.1/index.html#//00sq000000qm000000.
Why this would not be in the editor tracking "about" page, I have no idea!?!

00129: <value> Editor Tracking dates in database time zone

Desktop » Mapping » Publishing map services » Technical guide for map services » Prepare window messages

Services cannot include data where Editor Tracking is enabled and set to record dates in database time. Services can include data where Editor Tracking is enabled and set to record dates in Coordinated Universal Time (UTC). When publishing map services and feature services, this includes layers of stand-alone tables that reference datasets with Editor Tracking enabled. It also includes mosaic datasets with Editor Tracking enabled when publishing eimage services.

The <value> parameter covers the following:
�?�The mosaic dataset records
�?�Data frame has layers that record
�?�Data frame has layers and tables that record

Solution

To resolve this, the data in the map with editor tracking needs to use UTC. You must remove the layers or stand-alone tables in the map that record dates in the database's time zone, or disable Editor Tracking for these datasets.

If you need to publish these datasets and have Editor Tracking enabled, you will need to convert the time zone of the data to UTC. To do this, first disable Editor Tracking, then convert the dates to UTC and reenable Editor Tracking with the Record Dates in value set to UTC. You can convert the time values collected in one time zone to another time zone using the Convert Time Zone geoprocessing tool.

More information

Editor Tracking records who created or updated the features and when they did it. It is also required when you want to apply rules controlling edit permissions in feature services with ownership based on access control.

If you're planning on editing with the feature service, use UTC, a standard that is unaffected by differences in time zones. Since editors can apply edits from potentially anywhere in the world, UTC works well. UTC is also recommended if you'll be doing replication across time zones.

Learn more about tracking an editor's changes to data and how editor tracking works in a feature service

Zeke

ArcGIS 10.2 allows db time stamping - http://resources.arcgis.com/en/help/main/10.2/index.html#//00170000016p000000

GregDreaper

So why ESRI would default to UTC instead of DB time, I still cannot imagine. However to enable DB time tracking, I was able to make this work without the model. Although I felt like I was going around my rear to scratch my ear.

1. Add the fields by Enabling Editor tracking from the manage menu
2 Disable Editor tracking from the manage menu
3. Batch the Enable Editor tracking geoprocessing tool. (Note: you must select all the fields that you created from the previous steps. Also the "ADD_FIELDS" does not work for me.)

I am using 10.1 Build 3143.

Hope this helps some else.

Greg

KevinLynch

I've enabled editor tracking on multiple tables, but when I pick pick the workspace for the Iterate Tables tool, it automatically populates a table from the workspace which isn't a table I need to run the editor tracking on. I drag in the Enable Editor Tracking tool to the model and pick the first table in my geodatabase, but the model just loops on this table even though I've selected recursive. The model works fine with feature classes but won't for tables. Anyone have a work around?

Kevin

maybewillwork

I have File GDB with Feature Class "Damage". This features class has Editor Tracking Enabled becuase ArcMAP users requested that.

Then, I have to add some features via programming (C# ArcObjects). These features also have information who and when created/updated the features but I cannot set the value of the fields which are included in "Editor Tracking". The message is "Field is not editable".

I can update/set all other fields. Chagning the status programatically (FieldEdit_Editable_2 = true) does not help.

Any idea how should I manage the "Editor Tracking" fields via C# SDK ?

JonathanQuinn

Editor tracking is only available at 10.1, but no, it won't. Editor tracking is for tracking who created a feature, when they created it, who edited a feature, and when they last edited it. I'm not sure what tools in the toolbox will assist in your workflow.

LukeGilner

I have not figured out how to Enable Editor Tracking. Please help.
I have Desktop 10.0, just ugraded my geodatabase from 9.2. When I right click on a feature class there is no "Manage" menu.

Not really sure this is the solution I'm looking for anyway. I have a polygon feature class that I am cutting and merging pieces of one polygon to another. I need to record the ObjectID and another attribute of the polygons that I cut from and merge to. Recording this information manually is time consuming for hundreds of polygons. Will Editor Tracking record this type of information for me?

AndrewWharton

I thought I'd tried that and it didn't work, but I just tried it the way you said and it worked fine. Apparently I didn't check that box after all. That works much better. I did get some good model building practice in though. 🙂

JonathanQuinn

You should be able to use only the Iterate Feature Class iterator then the Enable Editor Tracking tool, and that's it. In the Editor Tracking Tool, enter the field names that you want created, and check the option to create fields if none exist. You don't have to use Add Field before, and then use the tool to set those fields as the editor fields. You can have the tool create the fields for you during the iteration. Anyway, I'm glad it (kind of) worked out.

AndrewWharton

Jonathan, thanks for the tip. I built a model using Iterate Feature Classes to add the four fields I needed, then a second tool to iterate through the data set and enable editor tracking using those fields, and using my database time.

I tried to make it one tool, but I can't run Enable Editor Tracking until the fields exist. When I try and add it as the last step after the fields are added as a precondition it still fails.

Still, I am able to do what I need.

AndrewWharton

I'll have to try that tool out. Thanks.

JonathanQuinn

The first problem with this is when I enter the version 10.1 dataset it causes an error saying the dataset is from an earlier version that doesn't support editor tracking.

I can reproduce this part of your post. If you're under maintenance, I'd suggest you get in touch with the Desktop team to see if it should be logged as a bug.

In the meantime, what you can do is use the Iterate Feature Classes iterator in ModelBuilder to iterate through each feature class within your dataset, and then use the Enable Editor Tracking tool on each feature class in the iteration.

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

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