For importing any data into ITSM when that data is non-ITSM data, old releases of ITSM, or Custom form data, Meta-Update is your answer.
We did a Clarify to ITSM Incident, Problem, Task migration in two months. On Friday evening, the Clarify ticketing system was shut down and on Monday the Clarify Support staff were working with their open tasks, tickets on ITSM. All historical data was transferred as well. For more information or trial licenses, please contact us. Ben Chernys Senior Software Architect Canada / Deutschland Mobile: +1 403 240 4377 GMT - 7 Email: Ben.Chernys_AT_softwaretoolhouse.com Web: www.softwaretoolhouse.com Check out Software Tool House's free Diary Editor and out Freebies Section for an ITSM 7.6.04 Forms and Fields spreadsheet. Meta-Update, our premium ARS Data tool, lets you automate your imports, migrations, in no time at all, without programming, without staging forms, without merge workflow. http://www.softwaretoolhouse.com/ -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of pritch Sent: August-14-12 13:59 To: arslist@ARSLIST.ORG Subject: Re: Importing data from another source form into the ITSM Incident form I had to do something similar (although the data came from a non Remedy system). I had extracts run into spreadsheets (csv) from that system (in this case it would be from the custom app), extracted the foundation data (people, groups, etc) and did a series of vlookups. I also had to do the initial load of tickets (used a field for the old system's legacy number), then extract some of the info from the created ticket, updated the spreadsheet which dealt with the attachments (basically work info) to reference the new ticket and loaded that info (also had to create a field with the path to the attachments. Wasn't really a headache - just a bit tedious. I did a couple test runs, documenting the steps, and then during a go-live weekend just loaded the whole thing. ----- Original Message ----- From: "Shawn Pierson" <shawn.pier...@sug.com> To: arslist@ARSLIST.ORG Sent: Tuesday, August 14, 2012 3:41:24 PM Subject: Re: Importing data from another source form into the ITSM Incident form What I was thinking was more along the lines of running an Escalation on his custom Form with a Push fields action. If the data has to be in a spreadsheet, then I would agree with using the DMT as LJ suggested, although it's quite a bit of work as well. Thanks, Shawn Pierson Remedy Developer | Energy Transfer -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Nathan Aker Sent: Tuesday, August 14, 2012 2:37 PM To: arslist@ARSLIST.ORG Subject: Re: Importing data from another source form into the ITSM Incident form Note that the HPD:IncidentInterface_Create form filters don't inherently fire on merge so in order to import data to this form and have it create Incidents you'll have to update all the filters and make them fire on Merge. We did this and note, we missed one filter that is not associated with the incident create form which sets the InstanceId field so make sure you hunt that down and make it fire on Merge as well before importing. We just did a one time load so I had to go back and manually set the InstanceId field on the records and never looped back to find the missing workflow. Nate. Nathan Aker ITSM Solution Architect McAfee, Inc. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Pierson, Shawn Sent: Tuesday, August 14, 2012 2:15 PM To: arslist@ARSLIST.ORG Subject: Re: Importing data from another source form into the ITSM Incident form I personally like using the HPD:IncidentInterface_Create form to do imports if I have something custom, especially if you're doing the migration on the same server that your data resides. It takes care of some of the lookups for you so you don't have to worry about it too much. Be sure your People data is populated, and try not to copy too many things over because it can be a hassle to make some of the data validate for non-required fields. Thanks, Shawn Pierson Remedy Developer | Energy Transfer -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Mark Lyndle Johnson Sent: Tuesday, August 14, 2012 2:00 PM To: arslist@ARSLIST.ORG Subject: Importing data from another source form into the ITSM Incident form Hello, My company recently purchased the ITSM suite 7.6.04 after running all of our ticketing processes on self-built custom-built Remedy forms. We're trying to import data from our old custom ticketing form into Incident, but we're running into a lot of errors in the process where some fields are not accepting the data and other fields (such as the customer info) are not displaying data at all after the import. Does anybody have a list of all of the fields that need to be populated in Incident in order for a data import procedure to function properly? Also, if the list had any recommended values for the fields, that would be great. Thank You, Mark ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" Private and confidential as detailed here: http://www.sug.com/disclaimers/default.htm#Mail . If you cannot access the link, please e-mail sender. ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.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" Private and confidential as detailed here: http://www.sug.com/disclaimers/default.htm#Mail . If you cannot access the link, please e-mail sender. ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.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" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
smime.p7s
Description: S/MIME cryptographic signature
