...
For the bulk update of System Elements in InfraLink, the data to be imported must be contained in a properly formatted CSV file.
System Element and Asset Prefixes
Since a System Elements Import can include System Element information as well as information for any associated Asset, 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
Please 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.
...
- Use the Choose File button to select the properly formatted CSV file that you have prepared for your bulk data import.
- Select the existing Top Level System for the System Elements being created or updated. All System Elements included in the CSV data file must belong to the same Top-Level System. If you wish to create or update System Elements under multiple Top-Level Systems, you must perform a separate Import for each.
- Select Default System Element (SE) Status for imported System Elements. When creating System Elements and a status is not explicitly specified in the CSV data file, this Default SE Status will be applied.
- Select Asset Status for any Assets being created or updated as part of the System Element Import. When creating Assets and a status is not explicitly specified in the CSV data file, this Default Asset Status will be applied.
- Indicate the Creating Effective Time for the Import. When creating System Elements, these date and time settings can be used to backdate System Element creation.
- Name the Import. It is helpful to enter an Import name that describes the Import action and purpose (e.g., "Power Feeders Import Rev-1")
...
If InfraLink identifies no exceptions within the data file, your bulk data will be successfully imported, and 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.