Bulk Import of Group Mappings

About this task

This section describes how to bulk import group mappings in SOTI Connect. In addition to the basic five-column *.csv file format used for bulk import of group mappings, there is also an extended bulk import *.csv file format available.

Bulk Import of Group Mappings

Procedure

  1. Navigate to Main Menu > Rules.
  2. In the left pane, select Automatic Group Mappings.
  3. Select the Import New Mappings icon. The Bulk-Add Mappings window appears.
  4. Select Upload File to choose and upload your .csv file.
  5. Optional: To replace all existing mappings with the ones in the uploaded file, select Delete all existing mappings.
  6. Select Generate to complete the import process.

CSV Format for Bulk Importing Group Mappings

The import group mapping files must be in *.csv format. Each row defines a new mapping with the following fields of information separated by commas. The extended bulk import group mappings *.csv file format supports up to eleven fields.
Note: The maximum file size is 120 KB.
Note: The first row of a bulk import group mappings file is a header and is not imported in the bulk-add process.
Column Description
1 Name of Mapping
2 Mapping Attribute
Options: "fqdn”, “iprange”, “ipmask” and “none”.
Note: The value of this column dictates the handling of columns 6 and 7.
3 Mapping Types

See Mapping Types in the Bulk Import of Group Mappings section.
4 (Optional) Source Group
5 Destination Group
6 Mapping Expression

Dependent on value of Mapping Attribute (column 2):

  • If column 2 has “fqdn”, this column has a mapping expression as described in the Bulk Import of Group Mappings section.
  • If column 2 has “iprange,” this is the start of the IP range to match against (for example, “172.16.141.49”).
  • If column 2 has “ipmask,” it is a valid CIDR-notation representation of an IP address and its associated network mask (for example, "198.51.100.14/24"). See Classless Inter-Domain Routing (CIDR) Notation Section for more details.
  • Ignored if column 2 has “none.”
7 Additional Mapping Expression

If column 2 has “iprange,” this is the end of the IP range to match.

  • Ignored if column 2 has “fqdn,” “ipmask,” or “none.”
8 Manufacturer
A case-sensitive string corresponding to a device manufacturer.
Note: To match, this string must appear exactly as it does under “Manufacturer” in the Device Details panel. For example, there can be no extra spaces or upper/lower case letter differences.
9 Model
A case-sensitive string corresponding to a device model.
Note: To match, this string must appear exactly as it does under “Model” in the Device Details panel. For example, there can be no extra spaces or upper/lower case letter differences.
10 Custom Attribute Name(s)
One or more custom attribute names, separated by commas.
Note: If providing more than one custom attribute name, the entire list must be in double quotes (for example, "MyIntegerAttribute,MyFloatAttribute").
11 Custom Attribute Value(s)
One or more custom attribute values, separated by commas.
Note: If providing more than one custom attribute value, the entire list must be in double quotes (for example: "1,2.5").
Note: The following notes apply to columns 10 and 11 of the extended *.csv file format for bulk import of group mappings:
  • Custom attribute values are only valid for automatic group mappings when given a single device type. If column 3 has more than one device type, then columns 10 and 11 are invalid.
  • The number of names must match the number of values provided. For example, if 3 custom attribute names are listed in column 10, for example: CA1,CA2,CA3, then column 11 must contain 3 correctly formatted custom attribute values.
  • Only Integer, Float, String, Boolean and Datetime custom attributes can be used in Automatic Group Mappings. Geolocation custom attributes are currently not supported.
  • A custom attribute with the given name must already exist in the active instance of SOTI Connect.
  • All custom attributes must be defined for the single device type provided in column 3.
  • For more information on valid custom attribute value formats, see Bulk Import of Custom Attributes.