...
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
...
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:
...
| 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 by with a System Elements import. To populate Asset Custom Fields, a subsequent Asset import would be necessary to bulk update those custom Asset attributes. |
...
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.
...