https://community.esri.com/t5/arcgis-pro-questions/editor-tracking-fields-not-populated-in-a-copy/m-p/1123148#M48735 <P>Hi all,</P><P>I have a question about copying and pasting features from a feature class hosted in an enterprise geodatabase with editor tracking enabled.&nbsp; We have a bit of an antiquated process for keeping track of historic features in which when a feature gets updated the original feature gets copied and pasted into a 'historic' layer for archiving and future reference if necessary.&nbsp; This layer keeps historical information from a variety of feature classes so the fields match but there are extra fields depending on the data coming to it.&nbsp; &nbsp;We've used this process for twentyish years and have never had issues until just recently.&nbsp; Recently we created a new feature class that has features in it that will need to be moved to the 'historic' layer.&nbsp; We have enabled editor tracking.&nbsp; We can create features in this new feature layer fine but when we copy a feature from this new feature class into the historical layer everything (attributes and geometry) comes over fine EXCEPT the editor tracking fields.&nbsp; Even though they are populated in the original feature in the original feature class all four come over as &lt;Null&gt;.&nbsp; I should also mention this behaviour only exists in ArcGIS Pro, the same behaviour is not exhibited in ArcMap.</P><P>I did mess around with the read-only settings on those fields with no luck.&nbsp; Has anyone else come across this?</P> Mon, 06 Dec 2021 21:02:20 GMT AJRStuart 2021-12-06T21:02:20Z https://community.esri.com/t5/arcgis-pro-questions/editor-tracking-fields-not-populated-in-a-copy/m-p/1123148#M48735 <P>Hi all,</P><P>I have a question about copying and pasting features from a feature class hosted in an enterprise geodatabase with editor tracking enabled.&nbsp; We have a bit of an antiquated process for keeping track of historic features in which when a feature gets updated the original feature gets copied and pasted into a 'historic' layer for archiving and future reference if necessary.&nbsp; This layer keeps historical information from a variety of feature classes so the fields match but there are extra fields depending on the data coming to it.&nbsp; &nbsp;We've used this process for twentyish years and have never had issues until just recently.&nbsp; Recently we created a new feature class that has features in it that will need to be moved to the 'historic' layer.&nbsp; We have enabled editor tracking.&nbsp; We can create features in this new feature layer fine but when we copy a feature from this new feature class into the historical layer everything (attributes and geometry) comes over fine EXCEPT the editor tracking fields.&nbsp; Even though they are populated in the original feature in the original feature class all four come over as &lt;Null&gt;.&nbsp; I should also mention this behaviour only exists in ArcGIS Pro, the same behaviour is not exhibited in ArcMap.</P><P>I did mess around with the read-only settings on those fields with no luck.&nbsp; Has anyone else come across this?</P> Mon, 06 Dec 2021 21:02:20 GMT https://community.esri.com/t5/arcgis-pro-questions/editor-tracking-fields-not-populated-in-a-copy/m-p/1123148#M48735 AJRStuart 2021-12-06T21:02:20Z