You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The import went well, but both approaches did not lead to the desired result:
I assumed Snipe-IT would group the license names and derive the checkouts from it - be it checkouts to users or assets (which both are present already in the system).
Instead I get an license entity named "Windows" with 1 checkout and 999 seats remaining. I assume some overwriting happening here.
Maybe I'm on the wrong foot here, but isn't the described desired outcome what one would expect? This may rather be a GitHub issue but I thought I check for your community wisdom first ;)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello *, this might be a no-brainer but i'm a bit confused how to manage checkouts to assets and users while importing licenses.
I have an CSV in the following form, checking out to assets:
I also tried a user checkout approach:
The import went well, but both approaches did not lead to the desired result:
I assumed Snipe-IT would group the license names and derive the checkouts from it - be it checkouts to users or assets (which both are present already in the system).
Instead I get an license entity named "Windows" with 1 checkout and 999 seats remaining. I assume some overwriting happening here.
Maybe I'm on the wrong foot here, but isn't the described desired outcome what one would expect? This may rather be a GitHub issue but I thought I check for your community wisdom first ;)
Thanks for your time!
Fabian
Beta Was this translation helpful? Give feedback.
All reactions