+1I have many locations that are incorrect and would like to make bulk corrections during import at runtime.
Curious as to why we can’t export the locations? Seems rather fundamental. Any ideas?
Also, consider if the Device42 locations are migrated into FS, then how are all the data elements going to be reconciled so it is normalized and actually useful.
Right now what is in FS is elementary and not easy to work with when trying to compartmentalize by region and such.
Hi!
I agree it should be possible to export locations in a simple way. The only way I can think of, and the way I have been handling it, is through the API where I can list all of my locations and make a file out of the response. An issue with this if I remember correctly is that you have to make a request for the different pages if you have many locations (which is not efficient at all in my opinion) so it is not possible in one call to list all the locations. Then editing them via API is no improvement at all compared to manually editing them in the GUI.
So to summarize, yes, location management seems to be currently very limited (as far as I know) and the only way to export the info is through API calls, while bulk editing is not really possible in any simple way.
+3Just had to do this myself to get a list of all locations so I could compare against used locations in assets and requesters to delete the excess, prior to creating a translation table for data being imported that has locations stored in a different naming format.
Exporting would be great. But so would actually being able to use the tree structure when filtering assets. It works in workflows, where you can say “belongs” but nowhere else. I want to filter to show all assets with a location that is nested within UK, I don’t want to have to select 15 different locations.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
