After a clone, the Activities log shows the correct comments and work notes but not the correct user who made them.

[Marshall Day]

After a clone, the Activities log shows the correct comments and work notes on Incidents but not the correct user who made them. Any ideas to correct this would be greatly appreciated.

[Marshall Day]

Varun,

Thanks for responding. Yes, a HI ticket has already been submitted. We are now down to discussing if the sys_audit table, which is in the excluded tables tab, is brought over, will this cause any issues with the target instance and if the amount of data being brought over will impact the process. Stay tuned for further information as I get it.

Marshall

[eduque]

Hey Marshall, we are experiencing the same thing, did HI ever get back to you?        

[Marshall Day · Accepted solution]

Earl,

I did receive some info from HI but the answer was not exactly what I wanted to hear. There is no real issue with the bringing over of the sys_audit table as far as time is concerned. Since the data is pulled before the clone there isn't a huge delay in the cloning. The issue was one of security. We have many, as probably most companies, secure incidents that deal with either personal info or HR type info. The information that is secure is stored in the same tables that the activity logs are stored so that was the reason we weren't bringing those tables over to begin with. There is no way to separate the secure data from the unsecured data in the cloning process.

So after a long discussion with our BA team it was decided that not importing secure data was more important than having the correct user ID on records that were in a non-production instance.

I hope this answers any questions you may have.

Marshall

[xavier_robert]

HI Marshall,

Thanks to your question, there is an article in the support knowledge base

Cloning - Activity formatter and Audit not showing correct user and time - Support and Troubleshooti...