licensstodaf asked a question.
How can we batch edit agreements? We have 200+ agreements that needs to go through various changes to standard and custom values. How do we edit these without doing it manually one by one? Thank you!
Option 1: Export the agreements to Excel, make your edits and then import again the modified records. Beware, I am not 100% sure what happens if you have linked licenses or devices to those agreements
Option 2: Use SQL to make your changes (dangerous and unsupported)
Ok, so if we have an agreement called, say "Microsoft 123", and imported an agreement with that exact name, Snow will update that agreement and not create a new one? Or does Snow match another value to know if it's an update or creation?
I will run a test on this now.
Thank you!
Expand PostThere is no official option in SLM to update an agreement. So my guess is that your import will not do what you want.
But I encourage you to try by creating a dummy agreement and testing an import of an agreement with the same name.
I would expect the import to work and you would have a duplicate agreement because each agreement is identified only by its CID and AgreementID:
All other items can be updated using an import template: Applications, Users, Licenses, Computers
I suggest you post an idea on the Ideas Board to ask for this feature
Expand PostCustom values are very easy to edit using SQL.
What are the types of standard values you need to edit?
As I suspected, I was unable to import changes because "agreement number already exists". We have a hosted solution and don't have access to the back end, and our supplier isn't keen on SQL as it is unsupported as you said. I was hoping that Snow had a solution to this common issue I'm sure many other customers have. It takes sooo long to update manually, and there should be a supported solution for this.
There is no official option in SLM to update an agreement. So my guess is that your import will not do what you want.
But I encourage you to try by creating a dummy agreement and testing an import of an agreement with the same name.
I would expect the import to work and you would have a duplicate agreement because each agreement is identified only by its CID and AgreementID:
I suggest you post an idea on the Ideas Board to ask for this feature