Skip to main content

Autodesk Vendor License Key to Vendor License Code Mapping

Introduction​

The autodesk-product-key-to-product-code.map is used to map Autodesk vendor license keys to its corresponding vendor license code. Each vendor license key is a unique alphanumeric string that identifies a particular software product, while the vendor license code is used internally by Autodesk's systems to recognize and validate the software version.

warning

Apply the configurations shown in the Open iT Core Server.

Configuring autodesk-product-key-to-product-code.map​

  1. Open autodesk-product-key-to-product-code.map in the Configuration directory, which is by default in C:\Program Files\OpeniT\Core\Configuration.

  2. Specify the feature to rename with the following syntax:

    Mapping Syntax
    MAP: <VendorLicenseCode>
    <VendorLicenseKey1>
    <VendorLicenseKey2>
    <VendorLicenseKey3>

    Empty lines are allowed — any line beginning with # as the first non-whitespace character is considered a comment. Globbing is also supported, allowing you to use several globbing patterns; however, remember that they are slower than exact matches. To make your mapping files more effective and efficient, refer to Optimizing Rules to Speed Up Rename or Mapping.

    In the mapping file, entries are case-insensitive, meaning that capitalization variations, such as 'Autodesk' and 'autodesk', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.

    Example
    MAP: ACD
    001G1
    001H1
    001I1
    001J1
    001K1
    001L1
    001M1
    001N1

    This example mapped 001G1, 001H1, 001I1, 001J1, 001K1, 001L1, 001M1, and 001N1 vendor license keys to ACD vendor license code, which is AutoCAD.

    You can also include custom configurations in this mapping file, such as default mapping, setting date limits on specific mapping entries, or creating nested maps.

  3. Save the changes.

This mapping may affect the following data types:

Next Steps?​

Proceed with data regeneration after configuring all the necessary mapping files to apply the changes in the real-time and historical reports.

For real-time reports:

Generating License Status Data

For historical reports:

Data Generation