Keep Feature Service Editor Tracking Data when using clone_items()

[alex_mapintel]

When using the clone_items() to clone a feature service from 1 agol account to another, ensure that Editor tracking attributes are not reset. Using something like

agol_dest.content.clone_items(items,copy_data=True)

currently resets the EditDate, CreationDate, Creator and Editor attributes in the destination AGOL feature service. They are set to the user that ran the clone_items() command and the date/time when the command was executed - which looses all edit tracking data.

The clone_items() function is not keeping the integrity of the data and honoring the concept of a "clone" i.e. "one that appears to be a copy of an original form.". Resulting in poor data tracking and more time spent post processing.

[ctalleygreenville]

Ugh, I guess since this is in the Ideas section that there is not a way to force the clone not to resent the editor tracking info?

This option would be very beneficial.  I am trying to find the best way to automate some sort of backup from AGOL to our enterprise portal for various reasons.  I keep hitting walls for each method I try. 

Thanks,