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.
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.
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.
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.
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. 🙂
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?
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.
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 ?
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?