For our Remedy 5.5-7.5 upgrade, we used the data management tool to import
incident and infrastructure change data.
I wrote a series of Perl scripts to parse csv exports of our 5.5 data and
put them into the data management tool's import format, and then copied the
Perl script's output into the .xls template files. We imported incidents,
changes, and their work log entries. (The Perl program read the 5.5 work
log and audit trail fields and parsed them into multiple 7.5 work log
entries.) These scripts were highly attuned to what we wanted to do in our
environment and assumed a bunch of default values for the imported records.
They were also highly attuned to what the 7.5 data management tool views as
correct/validated data.
IMHO using the data management tool for an upgrade would be impossible
unless you have your own version of a converter program to take the 5.5
data and put it in the 7.5 format you want.
Some parts of the data management tool are less optimal than others, and it
is very tricky to map some of the data. For example, we had several custom
Pending codes that could not be mapped through the tool--so we mapped them
to OOB pending codes and then bulk-updated the records in 7.5 once imported.
In my experience the tool is very slow, especially on the delete the
staging data step. It was much faster to have a DBA truncate the staging
tables than to try to delete the data through the client, and that was with
only ~20,000 work log entries. Pick a good sample set and then test A LOT
with that subset.
The workflow looked a lot like this:
Prepare for import (disabling Excel security pop-ups etc)
Try to import:
- put the .xls file in the right place
- run the csv conversion
- check the client-side logs generated by the conversion
- run the import
- check the client-side logs generated by the import
- try validating the data
- it didn't validate. Fix the .xls file, delete the staging data, and
repeat from the top
If you do this I HIGHLY recommend manipulating only the .xls files and
starting the whole process over from the top if there's an error. You will
be tempted to manipulate the generated .csv files but it will make your life
harder later.
Yours,
John Borwick
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Scott Philben
Sent: Tuesday, July 13, 2010 3:09 PM
To: arslist@ARSLIST.ORG
Subject: Using DataManagement Tool for Incidents?
Listers:
Anyone here use the 7.5/7.6 DataManagement tool for importing transaction
data into the Incident and Infrastructure Change forms? Does it work? Does
it work well?
Thanks.
-scott
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10
www.wwrug.com ARSlist: Where the Answers Are
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: Where the Answers Are
smime.p7s
Description: S/MIME cryptographic signature
