Import
Import is an efficient method when a lot of information is to be registered, for example license purchases.
Data can be imported manually on an occasional basis, or automatically on a regular basis. Manual imports are performed in Snow Management and Configuration Center (or in Snow License Manager) while automated imports are scheduled via the Web Configurator tool.
For a successful import of new or updated information in Snow License Manager certain information must be provided. For detailed information on required import data, and where the data can be found in Snow License Manager after the import, see the document Data Import Field Description.
Manual imports
The Import is a wizard-based function that allows for import of new items and update of existing items in the SLM database. A similar wizard is available in the Snow License Manager Web UI. Information can be imported to the predefined fields applicable to the category, and to most custom fields created in Snow License Manager (except custom fields of type currency).
There is also a dedicated wizard for import of agreements and licenses from a Microsoft License Statement (MLS).
Import file
The import source file can be in Excel or CSV format, and both source files with or without file headers can be used.
The column names (i.e. the header) of the import source file do not have to be the same as the destination field names in Snow License Manager. Mapping of source and target fields is done in the Field mapping step of the import wizard.
If the import source file has no header, index mapping can be used instead. This means that the fields of the import source file will be identified by index (column position 0, 1, 2, etc.) instead of text (column header).
Validation of data
To verify that only allowed data types and values are included in the import source file, the import functionality validates the data before it is imported. In the Preview step of the import wizard, errors are highlighted in red. Point to the field to see more information on the error.
Errors and conflicts that are highlighted in red prevent import/update of data.
Data can only be updated for an application that already exists in SLM. If the import data does not match an application name in the database, it is not possible to continue with the update of that particular application.
Preview
In the Preview step of the import wizard, errors like conflicts or invalid values are highlighted in red. Point to the field to see more information on the error. Rows highlighted in red will not be imported.
If the basic setting ALLOW_INCOMPLETE_LICENSES is enabled, fields that are missing the required information are highlighted in yellow.
Note
It is possible to continue with the import/update even if there are invalid rows. However, only rows with no or yellow highlights will be imported.
For License import, the import also verifies that the Stock-keeping unit (SKU) matches the entered license settings. Data that differs from what is expected is highlighted in yellow.
The metric of the application is defined by the SKU. If the import data does not match the expected metric there will be a warning, and you are given a chance to change the unexpected value in the source file before continuing with the import. It is possible to continue with the import even without changing, but note that there will be a mismatch in the database.
Automated imports
The Snow License Manager File Import Service can be used for automated and regular imports of data to SLM. The service is configured on the Import Service tab of the Web Configurator tool. For more information on the Web Configurator, see Appendix A – Web Configurator.
One import folder needs to be configured for each type of import, and the settings will apply to all imports of the same type.
Once the import folders have been configured, the Import Service will automatically look for and import data from files dropped in the folders. The files will be processed according to rules defined in the configuration.
For a successful import of data, certain data fields are required in the import file. Required fields depend on the type of import, as detailed in the document Data Import Field Description.