| Table of Contents | ||
|---|---|---|
|
| Note |
|---|
Access to IMMS tools and features is controlled by User Permissions. All features may not be accessible by all Users. Contact your Instance Administrator regarding User Permissions. |
Introduction
IMMS InfraLink maintains a Device/Equipment List with a details record for every System Element (e.g., device) within the System design.
System Elements can be populated or updated via bulk-data entry using the IMMS InfraLink Import feature. This document will serve as a guide for
This article provides guidance on the following topics related to the bulk creation or and bulk update of System Elements in IMMSInfraLink.
| Table of Contents | ||
|---|---|---|
|
| Note |
|---|
Access to InfraLink tools and features is controlled by User Permissions. All features may not be accessible by all Users. Contact your Instance Administrator regarding User Permissions. |
System Elements Import and Deployed Assets
When importing bulk To bulk create or bulk update System Element datarecords, you will use the Import System Elements/Assets form. While bulk Asset imports Assets are typically bulk created/updated via the Import Assets form (see "Assets Import" section), the bulk import creation of System Elements data may also include the bulk creation or update of the Assets that are associated with the created/updated those System Elements . (i.e., deployed).
See Asset Records See “Asset Definition” under the Assets and Inventory Management section for more information on the relationship between System Elements and Assets.
| Note | ||
|---|---|---|
| ||
Please note: Assets can only be bulk created in the Deployed status when done so as part of a System Element bulk-CREATE Import. Once a System Element record exists within an instance, an Asset association can only be created manually (i.e., via the UI). |
Data File for System Elements Creation
For the bulk creation of System Elements in IMMSInfraLink, the data to be imported must be contained in a properly formatted CSV file.
...
Since a System Elements Import can include System Element information as well as information for any associated Asset, IMMS InfraLink requires the following naming convention for certain column headers:
Prefix | Description |
D_ | Identifies a System Element (e.g., Device) attribute |
A_ | Identifies an Asset attribute |
NotePlease note:
- The Action column header does not require a prefix, as the Import action is related to the System Element and the same action will be applied to any imported Asset information.
- A Location column header does not require a prefix, as the Location for a listed System Element would automatically apply to any Asset associated with that System Element. The Location field value should be the Location path, with each path segment separated by a backward slash (e.g., “Building A\Floor 2\Room 231”).
Import File Data Columns
The following data columns (i.e., column headers) are required and must be populated for each line when creating System Elements:
...
- A_Make
- A_Model
- Unique Identifier, which will include either or both of the following:
- A_Serial #
- A_Owner + A_Asset Tag
| Note |
|---|
Please note, when creating Assets via a System Elements Import, only Asset native fields are supported. That is, Asset Custom Fields are not supported with a System Elements import. To populate Asset Custom Fields, a subsequent Asset import would be necessary to bulk update those custom Asset attributes. |
Data File for System Elements Update
For the bulk update of System Elements in IMMSInfraLink, the data to be imported must be contained in a properly formatted CSV file.
...
Since a System Elements Import can include System Element information as well as information for any associated Asset, IMMS InfraLink requires the following naming convention for certain column headers:
Prefix | Description |
D_ | Identifies a System Element (e.g., Device) attribute |
A_ | Identifies an Asset attribute |
NotePlease note:
- The Action column header does not require a prefix, as the Import action is related to the System Element and the same action will be applied to any imported Asset information.
- A Location column header does not require a prefix, as the Location for a listed System Element would automatically apply to any Asset associated with that System Element. The Location field value should be the Location path, with each path segment separated by a backward slash (e.g., “Building A\Floor 2\Room 231”).
Import File Data Columns
The following data columns (i.e., column headers) are required and must be populated for each line when updating a System Elements via bulk data import.
...
| Tip |
|---|
When updating bulk records via the Import feature, Users typically start the process by exporting the applicable records from IMMSInfraLink. See the Exporting Data for Update section for more information. |
...
Whether you are creating new System Elements or updating existing System Elements in IMMSInfraLink, you will follow these steps for importing the bulk data.
...
First, create a single ZIP file that contains all the files you wish to upload. The ZIP file can contain folders and subfolders. IMMS InfraLink will extract and process all files.
...
- Choose the ZIP file which includes all Custom Field files to be imported.
- Select the Top Level System for the System Elements being updated. All System Elements included in the Import must belong to the same Top-Level System. If you wish to update System Elements under multiple Top-Level Systems, you must perform a separate Import for each.
- Indicate the Custom Field to be updated or check the Use mapping file instead box if your ZIP file contains a mapping file for the files being imported.
- Select an Update behavior that is appropriate for your file import:
- Append to existing files
- Replace existing files
- Skip if there are existing files
- Enter an Update comment, which is text that describes your file import.
- Utilize Advanced Settings if you wish for IMMS InfraLink to apply certain file name rules when processing the imported files:
- Skip prefix in file name
- Skip suffix in file name
- Add prefix to file name
- Add suffix to file name
- Once all form fields are populated, click the OK button at the bottom of the form.
...
If there are any errors in the Import data file, IMMS InfraLink will alert you of these exceptions and reject the entire Import. That is, IMMS InfraLink will not partially process an Import.
All exceptions must be corrected in the data file before it can be imported. Correct exceptions in all specified line items and then repeat the Import steps listed above.
If IMMS InfraLink identifies no exceptions within the data file, your bulk data will be successfully imported, and IMMS InfraLink will return you to the view where you initiated your Import. The view should then include your new or updated records. The Import will also be listed in the Successfully Completed Imports list accessible via the "Show Completed" option under the Import button drop-down menu.
...