Easy Import Bulk Load Issues

[kailashthiyagar]

I m in Istanbul Release and we have bulk load requirement in PRD environmentwe

Using "Load Data" , "Transform Map" , we can do the bulk load in DEV environment but when it comes to PRD environment, whats the best way?

We would be getting multiple bulk load request and each time, we would like to test it in the DEV environment before doing it in PRD. We thought of doing it through Easy import process.

But the excel template which we download doesnt have the "List collector " fields even though the field has been selected in the list..

Whats the suggestion

ctomasi pradeepksharma abhinay

[mikereaves]

Kailash, The easiest way would be to export the entire table to XML on DEV and import the XML on PROD.   This method preserves the sys_id's. http://wiki.servicenow.com/index.php?title=Exporting_and_Importing_XML_Files#gsc.tab=0 Alternately you could continue to use your import set / transform map arrangement that you've been using in DEV when you're ready to move to PROD.   This presumes that all record formats are the same and that you've captured your transform maps in an update set that's already been migrated to PROD.   I hope this helps. Mike Reaves / Acorio Please mark the message as "helpful" or "Answered".

[kailashthiyagar]

If i need to export import files from DEV to TEST, i have to ensure i dont have any records in DEV before i import it into an xml file.. otherwise, my dev data will be pushed to PROD.. So every time, should i be wiping out records in DEV. Is that right?

Also, i have an Auto numbering, would that cause issues when importing the data in PRD

And with the transform Map approach, should someone be doing the same process in PRD as the one in DEV? Like "Load Data", Select Existing table and then run Transform Map?

[kailashthiyagar]

And also just of an interest, why "List collector Fields" not coming in the excel template when we download it

[Alikutty A]

I would prefer transform maps over the Easy import feature. The transform maps can be customized to add any level of validations that can prevent bad data from getting created in your system. Easy import is a direct load on the table and it can introduce data consistency issues (eg adding an invalid choice option). You should improve the error logging on your transform map scripts in such a way that you can directly load any data on production.

Thanks

Please Hit like, Helpful or Correct depending on the impact of the response