Andrew D asked a question.
The SLM Import is capable of upgrading existing licenses.
To do so, it requires the License ID that you usually won't see in the WebUI, exxcept in reports.
As an alternative, Snow allows to use the field "External ID" during import as well, but this is a field you would have to fill yourself.
So what I usually do is:
Hi Axel, thanks for this, appreciated.
I have followed this process but unfortunately SNOW is unable to map one of the mandatory values for the licence import to a row in the destination database... I will refer this to our SNOW provider.
Thanks again for the speedy response !
Hi Andrew,
can you share the column / value that is not matching?
Is it the ID or another field?
Regards, Axel
Hi Axel, thanks for this - it is the Legal Organisation field within the Licence import Template - a mandatory field
The error message is as follows:
Unable to map value "NUTH" to a row in the destination database
This is the same Legal Organisation value as our licences.
Andrew
Hi Andrew,
ah ok, there is one little thing you need to know about Organisation:
The highest node has to be named ROOT regardless what you see in the user interface.
If you want to add it to another node, the value would be like "ROOT,Europe,Italy,IT", so the entire path separated with comma.
Hi Axel, thanks again, I have logged a support call with our SNOW provider for this as I assume they will have the full view of the infrastructure.
Appreciate your assistance here,
Andrew
Hi Axel, managed to get this working now, thanks for your advise. Really appreciated.
Have a great weekend, Andrew
The SLM Import is capable of upgrading existing licenses.
To do so, it requires the License ID that you usually won't see in the WebUI, exxcept in reports.
As an alternative, Snow allows to use the field "External ID" during import as well, but this is a field you would have to fill yourself.
So what I usually do is: