The following table lists all the data types available for Tags in Ignition.
|Data Type||String Value||Integer Value|
|Document (JSON Document)||Document||29|
Array and Dataset Data Types
The Array and Dataset data types available on Tags allow for multiple data points to be stored in a single Tag. Configuring a Tag as an array or dataset is as easy as changing the data type in the Tag Editor.
Many OPC servers and drivers already support array type Tags, and now each element in the array can easily be represented with the array data types in Ignition. Additionally, array data types can be used with devices that do not support array types, and will instead expose each bit in the value. Because the core data type of each element in the array is the same, it is possible to apply Tag History, Alarming, or Scaling configurations onto the array, and these configurations will be inherited by each element.
Array Tag Write-Back
OPC Array Tags support writing back to the device. How this is done can vary, depending on the type of OPC Server in use. Some OPC Servers support writes to individual array elements, where a write would occur just like any other Tag write. However, some OPC Servers do not support individual element writes, which means the whole array will need to be written back to the array Tag, even if only a single element is changing.
Dataset Tags allow multiple rows and columns worth of data to be stored in a Tag. Each column is exposed as a separate folder in the Tag (i.e., the "name" folder in the image below). Dataset Tags can be driven by a query, so it's possible to query for multiple columns on a row in a single Tag. This is more efficient than using multiple query Tags (and thus multiple queries) to retrieve the same data.
While dataset tags are convenient, note that the Tag History system and Alarm system do not support tags with dataset types.
Valid data types that can be stored in dataset tags include the following:
The Document type allows a tag to have a JSON document as a value. Setting a Tag to this type will cause the value field to display an icon.
Clicking the icon will transition the Tag Editor into a JSON Editor, allowing you to manually write JSON directly to the value.
Click the + icon to add new members to the object. When finished, press Commit.
When saved, the value of the tag will render as a JSON document in the tag browser.