License import/update
Use the License import/update option to import information on new license purchases or update an existing license. To perform a successful import, the following information must be provided (mandatory fields):
Application name, Application part number, or SKU (stock keeping unit)
(selected alternative must be indicated under Identity mapping in the Import settings step of the import wizard)
Legal organization
Purchase date
Information indicated as “Required to get complete status” must be provided, otherwise the license purchase will be indicated as incomplete. An incomplete license purchase will not be included in the compliance calculation.
Destination field name in the import view | Data type | Required | Description | Example | Location in the user interface | Field name the user interface |
|---|---|---|---|---|---|---|
License ID | Number | No | ID of an existing license of which data is to be updated. To check the License ID:
Note: For license updates, the License ID field is required. If the License ID is not provided, the licenses in the import file will be treated as new licenses. | 486 | List all licenses | License ID column and Search for licenses | License ID column | License ID |
Application name | Text | Yes | Name of an existing application. | Adobe Photoshop CS4 | Edit license | Purchase tab | Application |
SKU (stock keeping unit) | Text | Yes | SKU number of an existing application. Note: For SKU numbers that are not in the database the license purchase will be imported as incomplete (with the setting ALLOW_INCOMPLETE_LICENSES enabled). | SFKJHDF34 | Edit license | Purchase tab | Stock-keeping unit (SKU) |
Legal organisation | Text | Yes | Legal organization that made the purchase. Delimiter between organization IDs is dependent on setting. Required to get complete status. For Snow License Manager, use the Organization Name in Snow Management and Configuration Center and not the Friendly name. For SAM Core on Snow Atlas: If the import is unable to map to the organization, find the identities for each organization node and add the identities to the import file. To find the Organization ID, also called GUID do the following:
| ROOT,IT,SUPPORT 5d0ed580-e3e9-4377-a944-9845e8fd6e54 | Edit license | Purchase tab | Legal organization |
Purchase date | Date | Yes | Date of purchase. Required to get complete status. Supported date formats:
| 2010-10‐28 | Edit license | Purchase tab | Date of purchase |
Metric | Text | No | The unit of measurement for the license. Required to get complete status. An empty value in this field will mark the license purchase as incomplete. Allowed values are:
| USERS | Edit license | Purchase tab | Metric |
Assignment type | Text | Yes | Provides information on how a certain license assigns licenses to relevant consumers. Available values are:
| Organization | Edit license | Purchase tab | Assignment type |
Is upgrade | Boolean | No | Defines if the license is an upgrade license or not. Allowed values are:
Note: The license purchase must be connected to an already existing base license, or it will be imported as an incomplete license (with the setting ALLOW_INCOMPLETE_LICENSES enabled). | YES | Edit license | Purchase tab | Upgrade license |
Upgrade from license ID | Number | No | ID of the license to upgrade from. Required to get complete status if Is upgrade is set to YES. To check the ID:
| 242 | License details| Purchase tab and Edit license | Base licenses tab | Upgraded from Application |
Base license quantity to upgrade | Number | No | Number of base licenses to upgrade. | 50 | License details| Purchase tab and Edit license | Base licenses tab | Base licenses to upgrade |
Quantity | Number | No | Number of licenses. Required to get complete status. If used for an upgrade license, this number should reflect the quantity that you are entitled to convert. Example: For metrics NUMBER OF PROCESSORS and NUMBER OF PROCESSOR CORES, the Quantity refers to the number of licensed processors/processor cores. | 50 | Edit license | Purchase tab | Quantity |
Subscription valid from | Date | No | Start of the subscription period. Required to get complete status if Is subscription is set to YES. Supported date formats:
| 2010-01-01 | Edit license | Purchase tab | From |
Subscription valid to | Date | No | End of the subscription period. Required to get complete status if Is subscription is set to YES. Supported date formats:
| 2011-12-31 | Edit license | Purchase tab | To |
Is subscription | Boolean | No | Defines if it is a subscription license:
If set to YES, Subscription valid from and Subscription valid to must also be defined. | Edit license | Purchase tab | License has a subscription period | |
Purchase price | Number | No | Value of the license purchase. | 100 | Edit license | Purchase tab | Purchase price |
Purchase currency | Text | No | Currency of the license purchase. | EUR | Edit license | Purchase tab | [no name] |
Cross edition rights | Boolean | No | Right to use the same and/or lower editions of the product. Allowed values are:
Note: Should only be enabled if the license is purchased with downgrade rights. | YES | Edit license | Purchase tab | Cross edition rights |
Downgrade rights | Boolean | No | Right to use the lower product version of the product. Allowed values are:
| YES | Edit license | Purchase tab | Downgrade rights |
Auto allocate (distribute) license | Boolean | No | Activates auto allocation. Allowed values are:
| NO | Edit license | Assignment tab | Auto allocate |
Maintenance includes upgrade rights | Boolean | No | The license includes a support or maintenance agreement. The field defines whether or not a maintenance agreement includes upgrade rights. Allowed values are:
Should be set to YES if the license is purchased with upgrade rights. Should be set to NO if the license is purchased without upgrade rights. Note: The Maintenance and Support fields should only be used if:
Note: If you update an existing license and include any of the Maintenance and Support fields in the license import, be aware that any previously entered data in the Maintenance and Support fields will be deleted from the database. | YES | License details| Maintenance and support | Upgrade rights |
Maintenance according to agreement | Boolean | No | Defines whether or not automatic upgrade will use agreement period. Allowed values are:
If set to NO and Maintenance includes Upgrade Rights is activated, an automatic upgrade period must be provided (in Maintenance and support valid from and Maintenance and support valid to), otherwise the license will be invalid. Note: The Maintenance and Support fields should only be used if:
Note: If you update an existing license and include any of the Maintenance and Support fields in the license import, be aware that any previously entered data in the Maintenance and Support fields will be deleted from the database. | NO | Edit license | Maintenance and support | According to agreement |
Maintenance and support valid from | Date | No | Defines what date automatic upgrade is valid from. Required for the license to be complete if Automatic upgrade is activated, and Maintenance according to agreement is set to NO. Supported date formats:
Note: The Maintenance and Support fields should only be used if:
Note: If you update an existing license and include any of the Maintenance and Support fields in the license import, be aware that any previously entered data in the Maintenance and Support fields will be deleted from the database. | 2010-10‐28 | License details | Maintenance and support | Period from |
Maintenance and support valid to | Date | No | Defines what date automatic upgrade is valid to. Required for the license to be complete if Automatic upgrade is activated, and Maintenance according to agreement is set to NO. Supported date formats:
Note: The Maintenance and Support fields should only be used if:
Note: If you update an existing license and include any of the Maintenance and Support fields in the license import, be aware that any previously entered data in the Maintenance and Support fields will be deleted from the database. | 2013‐08‐31 | License details | Maintenance and support | Period to |
Agreement number | Text | No | An external agreement number. This field can be left empty if Maintenance according to agreement is set to NO. If used, this agreement must already exist. Note: The agreement needs to exist prior to the license import. Also, the purchase date of the license must be within the agreement period. | HP19289182 | Edit license | Purchase tab | Agreement |
External ID | Text | No | Used to assign an ID from an external system, such as ERP, CRM or sales/order systems. | ABC123 | Edit license | Information tab | External ID |
Vendor/reseller | Text | No | Name of vendor/reseller that this license was purchased from. | Amazon | Edit license | Information tab | Vendor |
License proof location | Text | No | Location where proof of license purchase is stored. | Safe at the office | Edit license | Information tab | License proof location |
Purchase notes | Text | No | Enter license purchase specific information as free text. | Edit license | Information tab | Notes | |
Serial numbers/ license keys | Text | No | Serial numbers/license keys received for this purchase. | Edit license | Information tab | Serial numbers/ license keys | |
Installation media location | Text | No | Location where installation media is stored. | File server 1 | Edit license | Information tab | Installation media storage |
Purchase invoice reference | Text | No | Invoice reference number found on the invoice. | ADB00889912 | Edit license | Purchase tab | Invoice reference |
Product description | Text | No | Use the Product description to add either an own product description or the manufacturer's. | OfficeStd 2010 SNGL MVL | License details| Information tab | Product description |
Maintenance cost | Number | No | Maintenance cost per period. | 100 | License details | Maintenance and support | Maintenance cost |
Support cost | Number | No | Support cost per period. | 100 | License details | Maintenance and support | Support cost |
Maintenance and support notes | Text | No | Notes on the maintenance and support. | License details | Maintenance and support | Notes | |
Maintenance and support invoice | Text | No | Reference to the maintenance and support invoice. | SHB00375297 | License details | Maintenance and support | Invoice reference |
[Custom fields] | No | Import data to existing license custom fields. Supported custom field data types are:
| License details| Information tab | [Custom field name] |