Skip To Content

Enable or disable editor tracking

Editor tracking records the user name and the date and time a feature or record is inserted or modified in any way. This includes changes to feature geometry, system and user-defined fields, and processes that modify data in the background.

When you edit versioned data, dates are recorded when the edit is made. For example, if you made a change yesterday, and reconcile and post your changes today, the last edit date for the row in the default version is recorded with yesterday's date.

Reconciling versions with conflicts records the values in the editor tracking fields to the edited version based on the conflict resolution policy. Differences in editor tracking fields alone do not trigger conflicts. If there are no conflicts, the values in the editor tracking fields are applied to the edit version like values from any other fields.

You can record editing times in either Coordinated Universal Time (UTC) or the time zone where the database is located. UTC is the default setting and the best practice when workflow is distributed across time zones. The database time zone should be used only when workflow is confined to the same time zone.

User names are recorded differently depending on the authentication method used to log in and access a file or enterprise geodatabase as shown in the following table:

Operating system authenticationDatabase authentication
  • The typed login name is recorded as a case sensitive text string. For example, typing John is recorded as John and typing john is recorded as john.
  • The account login name is recorded.
  • You can append a realm to the recorded user name to better identify the user, for example, John@denver and John@seattle.

Note:

Editor tracking records user information only when existing data is modified. The following example scenarios are not recorded:

  • Schema changes that do not modify column values
  • Adding or deleting fields
  • Copying and pasting a feature class
  • Copying data with a data extraction tool
  • Converting labels to annotation
  • Importing an XML workspace document

Catalog pane

You can right-click a dataset in the Catalog pane Catalog Pane when you need to quickly enable tracking with predefined fields or stop tracking editor activity.

  1. On the View tab, in the Windows group, click Catalog Pane Catalog Pane.

    The Catalog pane appears.

  2. Right-click the dataset, feature class, or table and click Enable Editor Tracking on the context menu.
    • Press the Shift key to select multiple data sources.
  3. To stop recording editor information, right-click the dataset and click Disable Editor Tracking.

Geoprocessing tools

Consider using the editor tracking geoprocessing tools when you need to enable or disable specific fields.

To learn more, see Enable Editor Tracking.

  1. On the Analysis tab, in the Geoprocessing group, click Tools.

    The Geoprocessing pane appears.

  2. In the Geoprocessing pane, in the search box, type editor and click Enable Editor Tracking.

    The Enable Editor Tracking tool appears in the pane.

  3. In the Input Dataset text box type the feature class, table, or dataset name, or click Browse Browse and browse to it.
  4. Click the optional field drop-down arrows and configure the following:
    • Create Field—Stores the name of the user who created the feature or record
    • Creation Date Field—Stores the date a feature or record was created
    • Last Editor Field—Stores the name of the user who last edited a feature or record
    • Last Edit Date Field—Stores the date a feature or record was last edited
    • Record Dates in—Stores the date a feature or record was last edited
  5. If the fields do not exist in the database, check Add Fields to add them.
  6. Click the Record Dates in drop-down arrow and choose one of the following:
    • UTC (Coordinated Universal Time)—Record dates in UTC. This is the default.
    • Time zone of database—Record dates in the time zone where the database is located.
  7. Click Run Run.

Disable editor tracking

To disable one or more editor tracking fields, open the Disable Editor Tracking geoprocessing tool and uncheck the field.

To learn more, see Disable Editor Tracking.

ModelBuilder

If you need to customize how editor tracking is managed, you can run a geoprocessing tool in a model and use an iterator to cycle through multiple datasets, feature classes, or tables.

  1. On the Analysis tab, in the Geoprocessing group, click ModelBuilder Model.

    A new model view appears.

  2. In the Insert group, click the Iterators drop-down arrow and choose Iterate Feature Classes or Iterate Datasets.

    Only one iterator can be used per model. If you need to enable tracking on both feature classes and tables, you need to construct two models.

  3. On the canvas, double-click the iterator, or right-click it and click Open.

    The dialog box appears.

  4. In the Worspace text box type the name of the dataset or feature class, or click Browse Browse and browse to it.
  5. To iterate through all subfolders in the workspace, check Recursive.

    This enables tracking on all the feature classes in the specified geodatabase or dataset.

  6. On the iterator dialog box, click OK.

    The dialog box closes.

  7. In the Insert group, click Tools Tools.
  8. In the Geoprocessing pane, in the search box, type editor.

    The editor tracking tools appear in the pane.

  9. Drag the Enable Editor Tracking tool onto the canvas.
  10. Connect the iterator output feature class or dataset parameter to the Enable Editor Tracking tool input using one of the following methods:
    • On the Enable Editor Tracking dialog box, click the Input Dataset drop-down arrow and choose the iterator output feature class or dataset parameter.
    • Click the iterator output feature class or dataset parameter, drag a connector to the Enable Editor Tracking tool, and click Input Dataset.
  11. Double-click the Enable Editor Tracking tool, or right-click it and click Open.
  12. Specify the remaining parameters and click OK.

    The dialog box closes.

  13. On the ModelBuilder tab, in the Run group, click Run Run.