Update Organization information into SNOW

May 4, 2018 at 7:00 AM

Hello!

I am working with SNOW software updating company information and licensing metrics. My question right now is regarding the organization chart, how can I update this info to SNOW? There is any way to update this info in a .csv file?

I will get soon all the data regarding the entire employee information of the company and I need to update correctly the organization information ASAP.

Could someone help me with this task please?

Thanks!!

THowland
8 years ago
Hi Victor, You can do this in the Snow Management and Configuration Centre (SMACC). There is a useful guide on how to do this: https://community.snowsoftware.com/docs/DOC-1379-best-practice-guide-organisation-structure Hope this helps.
Expand Post
- VictorHidalgo
  8 years ago
  Hi Tyrone, Thank so much for your help. It was exactly what i was searching for. Additionally, ones the organization is successfully entered, how could we import an excel with all user organization details into the tool? I know we can add them one by one, but there is any way to upgrade all this info at ones? Thanks again for your time and help!
  Expand Post
  - THowland
    8 years ago
    Hi Victor, From my understanding Snow License Manager does not have the ability to import user information from an excel document. This requires a custom import into the SQL database, which can be achieved through Snow Professional Services if you do not have the technical capabilities onsite. Someone else asked this question recently (link below) and they were instructed to contact their Snow sales representative for more information from their professional services team. https://community.snowsoftware.com/message/6234-import-all-users Hope this helps.
    Expand Post
    VictorHidalgo
    8 years ago
    Thanks, Tyrone!
    Expand Post
    SamuelBaughan
    8 years ago
    Hi Victor, Would not the data be rather pulled from your Active Directory? It is very easy to upload that information to AD and Snow has this nice feature that will do the import for you into SLM. See this document under section 5.1 that explains how it is configured. Here is the description of this service: Information on new, changed, and removed computers and users is read from the Active Directory using log on credentials of a domain user. The inventory data is sent to a Snow Inventory Server, and is then presented in Snow License Manager. That is probably the best option. Now, if the information is not in AD or cannot be pulled from AD, here is some information: Disclaimer: This is for information purposes only, I do not recommend using this without prior advice from a Snow specialist . When you update a user's details from the SLM interface, the stored procedure that gets executed is this one along with its 18 parameters: You can see it in a SQL Profiler session. It gets captured as follows: exec UserInfoAddUpdate @CID=N'1', @UserID=N'123', @OrgChecksum=N'-987654321', @Fullname=N'xxxxxx, yyyyyy', @DisableAutoEditing=N'1', @PhoneNumber=N'*12345', @MobilePhoneNumber=N'', @Email=N'yxxxxx@zzzzz.aaa', @Location=N'', @RoomNumber=N'', @CustomFields=N'<customfields> <field id="38" value="" updated="1" /> </customfields>', @ApplicationList=, @UpdatedBy=N'Qwerty Poiuyt', @StatusCode=N'0', @QuarantineDate=, @QuarantineOverride=N'0', @MultiEdit=N'0', @ForceCustomFieldCrunch=N'1' You see the pattern. The first 3 parameters can be found easily from the appropriate tables and knowing that @UserID is set to to create a new user. So if there is a need to bulk update data, the code can probably easily be written and checked by a Snow specialist . I am not a Snow specialist. Regards
    Expand Post
    SamuelBaughan
    8 years ago
    Hi Victor, Would not the data be rather pulled from your Active Directory? It is very easy to upload that information to AD and Snow has this nice feature that will do the import for you into SLM. See this document under section 5.1 that explains how it is configured. Here is the description of this service: Information on new, changed, and removed computers and users is read from the Active Directory using log on credentials of a domain user. The inventory data is sent to a Snow Inventory Server, and is then presented in Snow License Manager. That is probably the best option. Now, if the information is not in AD or cannot be pulled from AD, here is some information: Disclaimer: This is for information purposes only, I do not recommend using this without prior advice from a Snow specialist . When you update a user's details from the SLM interface, the stored procedure that gets executed is this one along with its 18 parameters: You can see it in a SQL Profiler session. It gets captured as follows: exec UserInfoAddUpdate @CID=N'1', @UserID=N'123', @OrgChecksum=N'-987654321', @Fullname=N'xxxxxx, yyyyyy', @DisableAutoEditing=N'1', @PhoneNumber=N'*12345', @MobilePhoneNumber=N'', @Email=N'yxxxxx@zzzzz.aaa', @Location=N'', @RoomNumber=N'', @CustomFields=N'<customfields> <field id="38" value="" updated="1" /> </customfields>', @ApplicationList=, @UpdatedBy=N'Qwerty Poiuyt', @StatusCode=N'0', @QuarantineDate=, @QuarantineOverride=N'0', @MultiEdit=N'0', @ForceCustomFieldCrunch=N'1' You see the pattern. The first 3 parameters can be found easily from the appropriate tables and knowing that @UserID is set to to create a new user. So if there is a need to bulk update data, the code can probably easily be written and checked by a Snow specialist . I am not a Snow specialist. Regards
    Expand Post
RCPhilly
5 years ago
Anyone have a copy of https://community.snowsoftware.com/docs/DOC-1379-best-practice-guide-organisation-structure? It doesn't seem to exist anymore

Expand Post