Create the Configuration Files
- The configuration files for one or more additional views were created.
- Check the delimiters in your EDE file. Open the EDE file using a text editor.
- Using a text editor, create a new Hierarchy-User.txt file or Hierarchy-Logical.txt file.
NOTE: The mapping files must be in the same folder as the import files.
- (Optional) Add the correct code-page information for encoding. For example, !encoding!UTF-8.
- (Optional) In separators-1 change the default separator (;) for the EDE file according to your requirements.
- (Optional) In separators-2 change the delimiter for the State text and Unit text columns according to your requirements.
- Define the Reference column for hierarchy mapping (default column = keyname).
NOTE: If the Keyname field is empty on an object, no logical or user view is created for this object. The object is, however, displayed in Management View.
- Define the following entries for each used hierarchy level. (For example, Location, Building, Floor and so on):
- Hierarchy Separator for the reference column (for example, _ ' :). Required for parsing the various hierarchy levels.
- Minimum length of the corresponding hierarchy level.
- Maximum length of the corresponding hierarchy level.
NOTE: For fixed field lengths, the minimum and maximum length must be the same and the hierarchy separator left out.
- (Optional) A description of the corresponding hierarchy level.
NOTE: The description text for a virtual hierarchy object is displayed in System Browser.
- Select File > Save.
- Copy the file to the folder where the EDE file is located.
Example of Hierarchy-User.txt or Hierarchy-Logical.txt file
!encoding!utf-8
#separators-1#;
#separators-2#,;
:column-name:keyname
;Family;BACNET_Fire
+EOType-Aggregator+EO_BA_AGG_1
?EOType-Folder?EO_BA_FDR_1
,',1,100
,',1,100
,',1,100
,',1,100
,',1,100
,',1,100
See also BACnet Fire 3rd Party TXT Files.
The selected files are checked for proper syntax prior to import. If an error message is displayed, click Open Log for additional information.
If the Hierarchy-User.txt and Hierarchy-Logical.txt files are used, the minimum and maximum length of the hierarchy level of the data point is checked. An error message is displayed if it is too short or too long. The data point is created in the database, but not visible for the corresponding view.