1

I am trying to update a few fields on our devices in inventory (Owner and Location) through the bulk import method (ruby bulk_import.rb - e username@domain -p password -s server file.csv). Unfortunately, the import runs fine (says import is successful) but the fields are not updated. Any ideas?

2 Spice ups
2

It should update the devices if the serial number and name fields match (they’ll need to be included in the CSV).

Please double check the .csv and let me know if those fields are in place. If they aren’t then the script may have created duplicate devices in the Inventory.

3

The serial number and name of the device were both listed in the csv and were identical to what was in inventory (only changed device owner and location from the original csv). After running the script there were no duplicate devices and the last update time was not changed on the updated items. However I did add a new device to the csv, which was successfully added to the inventory during the same run as the “updated” items.

4

Interesting. It’s unlikely, but there may be a caching issue taking place. Please try restarting Spiceworks and let me know if there information is updated afterward.

Thank You!

5

I have the csv, armo the script with the correct fields and not actuliza, the strange thing is that in the previous version of spice if fucionaba and the only thing that has changed, I see people as the same thing happened but I see that someone has found some solution, any thoughts on this? Thank you.

6

Any updates on this at all? I have used the import script to update a test device which included the serial Number and the name and purchase price which i wanted to update. The script said importe device but purchase price has not been updated.

7

Hey Guys,

Quick update- I don’t have a time frame or outlook at the moment, but this is a known bug we’re currently working to resolve.

8

This is still a problem in v7.2 when is this going to be fixed? We need to run a bulk update of purchase prices etc. Is there absolutely no indication to when this will be fixed?

Thanks

David

9

Sorry for the inconvenience on this one. We’re still working on the issue, but I unfortunately don’t have a time frame. I’ve included a link to the release notes page below in case you’d like to keep an eye out: