Hi Doug
I *think* he is referring to importing workflow objects, not form data. The modified date is indeed set to the current date in that situation. Even more annoying for me is when working with Application objects, adding a new form to the Application resets the last modified time for *all* forms in the Application. If you are trying to track changed objects by when they were last modified, for example to prepare a delta definitions file, this 'feature' is really troublesome. Regards David Sanders Solution Architect Enterprise Service Suite @ Work / e-ServiceSuite tel +44 1494 468980 mobile +44 7710 377761 email david.sand...@westoverconsulting.co.uk web http://www.westoverconsulting.co.uk <http://www.westoverconsulting.co.uk/> http://www.e-servicesuite.co.uk <http://www.e-servicesuite.co.uk/> <http://e-servicesuite.com/> Description: cid:image001.gif@01CCE023.38E7E320 ITIL - SaaS - On Premise From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Mueller, Doug Sent: 12 April 2012 17:54 To: arslist@ARSLIST.ORG Subject: Re: Transferred Object "Last Changed" Value Set to Timestamp ** Everyone, If you use the Import Tool, simply map the "Last Modified Date" and "Last Modified User" fields from the source to the target. It uses the ARMergeEntry() call and if those fields are supplied, the AR System Server will retain them and not set these fields to the current values. If not mapped, they will set these fields to the current values. Now, I would expect you to be able to map these values as well when using other transfer sources like Migrator. IF this is not possible, then there is a limitation in the product and you should definitely send in a problem report so it can be addressed. I import data all the time from old sources all the time and the dates and names are all retained as I map all fields into the system. Take a look at the fields you are mapping and add these if they are not defined. Again, if you cannot include these fields in the mapping for some transfer mechanism or if you do and the values are not retained, then there is a problem that needs reporting and fixing. I know the Import Tool does the right thing because it is working for me. So, you could use the Import Tool to import the data with these fields mapped to get the data transferred correctly today even if there is a problem with another tool. I hope this helps, Doug Mueller From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of David M. Clark Sent: Thursday, April 12, 2012 6:24 AM To: arslist@ARSLIST.ORG Subject: Transferred Object "Last Changed" Value Set to Timestamp ** Folks, My transfers from a 6.3 server to a 7.1 server via Migrator 7.1.00 p006 set the Last Changed Time on each imported object to the time of creation on the server. I thought this might be a problem with the Migrator "mask" setting, but the same thing happens when definitions that have the correct date are imported via the 7.1 Admin Tool. Any ideas? Thanks, -David _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
<<image001.gif>>
