How to Import Custom Tag Properties (version 24)

Properties are metadata attached to the tags stored in the Historian. These properties can be stored in the Historian or be configured to be stored in an external SQL database (see How to Configure External Property Storage for Populating Metadata in Virtual Views). The method for importing properties mentioned here are those that will be stored in the Historian and appear in the yellow PROPERTIES window when drilling down to the tag level in a DataSet.

Although properties are often logged along with the data through a Collector source, not every Canary Collector has the option of creating custom properties (e.g. OPC DA Collector). Therefore, an alternative for importing properties is required.

There are two locations within the Canary Admin where the user can import properties:

1. At the DataSet level
2. Within a specific DataSet

Importing properties at the DataSet level allows the user to attach properties to tags across multiple datasets at once.

1. How To Import Properties at the DataSet Level

1. Open the Historian tile in the Canary Admin and click the white down-arrow in the top left HISTORIAN window.
2. Select the IMPORT PROPERTIES button. A new menu will appear prompting the user to browse for a CSV file containing the tag names and properties to be processed. The first column should contain the tag names (INCLUDING the prepended DataSet name) and any number of subsequent columns for each property the user wishes to import. (The ImportForMultipleDatasets.csv attached at the top of this article is an example of this.) 
3. Once the CSV file is selected, click ok. A RESULTS menu will appear indicating if the import was successful.

2. How to Import Properties Within a Specific DataSet

1. Open the Historian tile in the Canary Admin and select the DataSet you wish to import properties for.
2. Click the yellow down-arrow in the bottom-left DATASET window and select IMPORT PROPERTIES.
3. A new menu will appear prompting the user to browse for a CSV file containing the tag names and properties to be processed. The first column should contain the tag names (EXCLUDING the DataSet name) and any number of subsequent columns for each property the user wishes to import. (The ImportForSingleDataset.csv attached at the top of this article is an example of such.)
   
4. Once the CSV file is selected, click ok. A RESULTS menu will appear indicating if the import was successful.