Run import
On the Home menu, select Import data.
The Import data view appears.
Select import type to start the import wizard.
Upload a data source
Select Browse and then select the import source file.
If the import source file is a CSV file, select used Delimiter from the list. Otherwise, leave the default value.
Select Next.
Configure import settings
Manage settings for the data import according to the following sections. Available import settings depend on the type of import/update.
Select Next.
Settings for all imports/updates
In the New organization action list, select how to handle organizations that exist in the import source file but not in the Snow License Manager database. The options are described in the following table.
Options for New organization action | Description |
|---|---|
Do nothing | Unknown organizations will be ignored. However, information on organization is required for a successful import. The field will be highlighted in the Preview step and it will not be possible to import data for that particular row. |
Create | The system will create the new organization node, either directly under the root (for example: ROOT/[new organization node]) or according to the path in the import source file (for example: ROOT/IT/[new organization node]). |
License import settings
In the Identity mapping section, select which identity field to use when a license is mapped to an application:
SKU (Stock-keeping unit)
Application Name
Application Part number
Computer update settings
In the Obsolete computer action list, select how to handle computers that exist in the Snow License Manager database but not in the import source file. The options are described in the following table.
Options for Obsolete computer action | Description |
|---|---|
Do nothing | Nothing will happen to the obsolete computers. |
Inactivate | All obsolete computers will be inactivated during the import. An inactive computer does not require licenses for its installed applications and is not included in the compliance calculations. |
Archive | All obsolete computers will be archived during the import. An archived computer is removed and all licenses currently attached to it are released. |
Delete | All obsolete computers will be deleted during the import. A deleted computer is removed from the system; all computer details are deleted and all attachments to users, agreements, licenses, etc. are released. |
A computer that has been archived or deleted during import cannot be restored. If you have an import file that does not include all the computers in the database, only select Archive or Delete if you really want to remove them from the system.
Note
It is possible to limit the obsolete computer action to certain computers in the database by a configuration setting in Snow MACC.
Custom Object update settings
In the Object type list, specify the object type that will be updated. Depending on object type, different destination fields will be available in the Field mappings.
License assignment import settings
In the Assignment action list, select to add to existing assignments on a license, or to replace them completely.
Map source and destination fields
Map the column headers of the import Source file to the corresponding Destination fields in Snow License Manager. Mandatory fields are marked with an asterisk * and must be included in the import source file. The fields to be mapped depend on type of import/update.
If the source file has no header, Map by index can be used instead.
Map and configure identifiers
For updated information to be mapped to the correct items, an identifier must be selected. Depending on how the import file looks like, select to identify by using the file header or to map by index.
To map and configure identifiers:
To map by index, select the Map by index check box.
In the Map identifiers destination list to the right, select identifier.
In the Map identifiers source list to the left, select column header or column position where information on selected identifier is found.
To remove any spaces in the beginning or the end of a data value, select the Trim leading or trailing white space check box.
Map and configure field mapping options
To configure a field mapping, select the Mapping
icon to the right of the field name.A dialog box appears.
To remove any spaces in the beginning or the end of a data value, select the Trim leading or trailing white space check box.
To map by index, select the Map by index check box.
Enter a Default value to be imported if there is no value in the source field.
Optionally, enter a Prefix (text and/or number) to be added in front of all imported values. This can be used for separating objects from different sites. For example, enter “SE_” to be added in front of all computers located in site Sweden.
For update of existing items an option is included for any existing custom fields. In the Empty value action list, select how the system shall handle an empty field in the source file when updating the database:
Do not update - The database will not be updated.
Remove value - The database will be updated with the empty (blank) value.
Note
If a Default value has been defined, see above, the Empty value action will not apply.
Select Save. The Mapping icon to the right of the field name is replaced by an exclamation mark
indicating that settings have been made.In the Source list, select column header or column position where information on selected Destination field is found.
Repeat the previous steps for every field mapping.
Select Next.
Preview of imported data
In the Preview of imported data, errors, missing information and data that differs from what is expected are color highlighted, according to the following table.
Color of field | Description |
|---|---|
Yellow | If the Incomplete licenses functionality is activated (which is done in Snow MACC), fields that are missing the required information are highlighted in yellow. For License import, the import also verifies that the Stock-keeping unit (SKU) matches the entered license settings. If import data does not match the expected metric, there will be a warning. You may want to change the unexpected value in your source file before you continue with the import. It is possible to continue with the import even without changing, but please note that there will be a mismatch in the database if you do. |
Red | Errors like conflicts or invalid values are highlighted in red. Rows that have any fields highlighted in red will not be imported. |
It is possible to continue with the import/update even if there are invalid rows. However, only rows that are not highlighted or highlighted in yellow will be imported.
To preview the data:
To see more information about a highlighted field, point to the field.
To export the entire preview to an Excel file, select Export all rows.
To export only rows with errors, select Export invalid rows Descriptions of the errors/warnings will be included in the file. This may help you to correctly create the source file, with the right fields and content.
To go back and correct field mappings and import settings, select Previous.
To start the import, select Next.
Import
The progress of the import is displayed.
When completed, select Finish.