Cleaning up system

[Jeffce]

Anyone know or have a link to Best Practices for cleaning up the system with old transform maps???

Thanks JJ

[Jacob_Andersen]

Jeffce,

What do you mean by 'cleaning up the system w/ old transform maps?'   We clean out demo data before going live and we sometimes clean up code before promoting an update set to an instance.   Are you referring to one of these?

[Jeffce]

Well i use a different transform map each time i upload data such as assets, I am 2 years into servicenow, i have learned a lot but still a lot to go. I know there is a cleanup for import sets, but how well does it work, what will it harm in removing older transform maps (Outside of the LDAP), I guess i would like to learn a little more of they hows and why's to keep the system running smooth. Thanks Jacob for answering and for everyone like you that are there to answer questions and lend a hand all the time...

JJ

[Jacob_Andersen · Accepted solution]

Jeffce,

I think that the first thing to do is to see if you can use the same transform map and the same import set table for data that you import regularly.   Instead of using the 'import data' module, I'd set up a new data source where you can pull data from a spreadsheet, JDBC (database), etc.   This way your import set tables stay clean and you can reuse your transform maps.

The cleanup function by SN works well, though.   You should not be afraid to use it if you want to delete import set table data and/or associated transform maps.