You can use the Excel file to add an InfoSource to a point and set its properties.
The system creates (at least one value is needed in one of the sub columns) or updates an InfoSource.
Example
An InfoSource is created inside the component described in the row
InfoSource | ||||||||
Create/update subComponents | ||||||||
description | sourceDisplayName | mnemonic | notes | syncUp | syncDown | inherit | markers | tag:b:myTag{baja:Boolean} |
myDescription | %parent.displayName% | myMnemonic | myNotes | false | false | true | hs:heat | true |
Add a colum named "InfoSource" on the first line. Then you can define those following subcolumns (none of them are mandatory)
markers: to define all the markers tags
several tag subColumns. value using the following format: tag:dictionary:key{Niagara TypeSpec of the slot}. Example: tag:b:myTag{baja:Double}. If no TypeSpec is given, the system will use a BString by default. Similarly to the Tag subColumns, you can set the flags during the import.
The tag subClumn will only be able to import/export SourceTags. |
baja:Marker
baja:String
baja:Integer
baja:Long
baja:Float
baja:Double
baja:Boolean
baja:Ord
baja:DynamicEnum (the cell value must be the tag, not the ordinal)
baja:AbsTime (the value text must strictly conform to the ISO 8601 standard format of "yyyy-mm-ddThh:mm:ss.mmm[+/-]hh:mm")
Simply add values to the slots you want to update.
If there is a value in the slot associated to a column, the slot's value will be exported to the cell.
SPECIAL CASE FOR SOURCETAGS
It's not possible to update a readOnly SourceTag. However you can replace the "tag:" prefix with the "tagReadOnly:" prefix in your subColumn (example: tagReadOnly:b:myTag(baja:Double). This prefix will allow you to export the SourceTag to Excel. On the import the SourceTag will be created if it doesn't exist or ignored if it's already there as it's a readonly SourceTag.
Here is the file used in the above import example. Download it, try importing it and see the result.