Importing Hierarchical Setup Items
The import spreadsheets for both Buildings and Accounts & Meters are structured in a way that allows the hierarchical relationships between items to be defined.
In both templates, some columns are only used when a row represents a "Parent" item (like an Organization or Account); other columns are only used when the row represents a "Child" item (like a Building or a Meter). This provides two benefits when viewing the spreadsheet data:
- It is easy to differentiate different types of objects. In a file that contains both Organization nodes and Building nodes, for example, a user can quickly see which rows represent each item type.
Using separate column and row combinations for hierarchy levels provides a visual representation of the Parent-Child relationship even before the data is imported into UtilityTrac.
IMPORTANT NOTE: In templates that provide a means for relating Parent/Child items, the Parent item must have been created before it is referenced as a Parent. Parent and Child items can be defined in a single import file as long as the Parent item is defined in a previous row of the import file, or if the Parent already exists in the UtilityTrac database. But if a Child (e.g. Building or Meter) references a Parent item that does not exist, the Child item will not be created. Instead, it will be added to the error file created at the end of the import.
If a Parent item is not in the database, and the import row defining the Parent item contains an error, all Child items that reference that Parent will not be created.
Sample Organization and Building File
As an example, consider a university that wants to set up the Buildings & Meters hierarchy by department. If they manually created each item in the tree, they would probably first create Organization nodes for each department and then create individual buildings under each department. The resulting Buildings & Meters tree might look like this.
To create this same structure using the Buildings Setup Import file, the hierarchy would be represented as follows (using the first six columns from the import template)
|Organization Code||Organization Name||Organization Type Code||Parent Organization Code||Building Code||Building Name|
With this file structure it is easy to distinguish between items that are only Organization nodes and those that represent actual buildings. The Parent/Child relationship is also apparent.
Accounts and Meters
The import file for Accounts and Meters is structured in a similar fashion. Accounts and their related columns of data are visually separated from the columns that represent the meters, highlighting their relationship.