00129: <value> Editor Tracking dates in database time zone
In this topic
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 image 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 as an image service, a service with feature access capabilities or a service with WFS-T capabilities, 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.
If you need to publish these datasets as a map service or image service and have Editor Tracking enabled, turn off the field visibility for the editor tracking date fields for the layer or stand-alone table in ArcMap.
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