Editor Tracking – High Precision Date Fields issue in ArcGIS Pro.

[MikeLongtine]

I have an issue, and it appears ArcGIS pro has an issue as well with the editor tracking date fields in Arc GIS Online.  These fields (created_date, last_edited_date) are represented as High Precision in AGOL.  If I Export the features to a new geodatabase, I cannot turn on editor tracking using the High Precision date fields, I do not get the option to use the created_date, last_edited_date.  When I chose the Use Default option, I get an error (EnableEditorTracking: ERROR 001217). 

If I export to geodatabase from the ArcGIS online interface – download – Unzip and do the same process, the date fields are no longer high precision. This works for my process, but is much slower than doing it in ArcGIS Pro.

Has anybody else seen this behavior and is there a possible bug or workaround?

ArcGIS Pro 3.4.0

[PeterKnoop · Accepted solution]

This is a open bug with Enable Editor tracking in ArcGIS Pro. You can ask Esri Support to attach you to BUG-000164474 to track progress on resolving the issue.

Another workaround, though also time consuming, is to add two new fields that are low-precision date fields, calculate their values from the corresponding high-precision fields, delete the high-precision fields, rename the new fields to the original names, and then turn on editor tracking. You can implement that workflow in a Notebook for convenience and speed, if you find yourself doing it regularly.

[MikeLongtine]

Here is some python which does the workaround:

# Import system modules
import arcpy

# Set environment settings
arcpy.env.workspace = "D:\\ArcGISProjects\\Default.gdb"

# Set local variables
inFeatures = input("Prompt message: ")
fieldName1 = "created_dateNEW"
fieldAlias1 = "created_dateNEW"
fieldName2 = "last_edited_dateNEW"
fieldAlias2 = "last_edited_dateNEW"

# Add new fields
arcpy.management.AddField(inFeatures, fieldName1, "DATE", field_alias=fieldAlias1)
arcpy.management.AddField(inFeatures, fieldName2, "DATE", field_alias=fieldAlias2)

# Copy the data from the old fields to the new fields
arcpy.management.CalculateField(inFeatures, fieldName1, "!created_date!")
arcpy.management.CalculateField(inFeatures, fieldName2, "!last_edited_date!")

# Delete the old fields and rename the new fields to the old field names
arcpy.management.DeleteField(inFeatures,["created_date", "last_edited_date"])
arcpy.management.AlterField(inFeatures, "created_dateNEW", "created_date", "created_date")
arcpy.management.AlterField(inFeatures, "last_edited_dateNEW", "last_edited_date", "last_edited_date")

[CarmenDurham]

I am at 3.3 and seeing this behavior as well.  Thank you two for posting all of this.