Skip to main content
Version: 8.1

Tag Data Types

This page details the different data types that can be applied to standard tags.

The data type of a tag is determined by the Data Type property, which is accessible from the Tag Editor. The tags system will attempt to coerce any raw incoming value (for example, from OPC or a SQL query) into the desired type.

The following table lists all the data types available for tags in Ignition.

Data TypeString ValueInteger Value

Changed in 8.1.29
Prior to 8.1.29, the Siemens driver does not support Ignition tag's DateTime type. In these cases it is recommended to extract each byte in the Siemens DATE_AND_TIME value item, storing each into a separate Ignition tag. Then use an expression tag to combine each byte into a human readable datetime.
For 8.1.29+, the Siemens driver supports DateTime data types for the following Siemens devices:
  • S7-300
  • S7-400
  • S7-1500
  • DateTime8
    Text (Deprecated in 8.1.8)Text10
    Byte ArrayInt1Array17
    Short ArrayInt2Array18
    Integer ArrayInt4Array11
    Long ArrayInt8Array12
    Float ArrayFloat4Array19
    Double ArrayFloat8Array13
    Boolean ArrayBooleanArray14
    String ArrayStringArray15
    DateTime ArrayDateTimeArray16
    Binary DataByteArray20

    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.


    Most OPC device drivers do not support array and dataset data types. These types work best when used on query tags or memory tags. When working with arrays via our OPC UA device drivers, it is recommended to create Ignition tags for each array element instead of using an array data type tag.

    Array Tags

    For OPC servers and drivers that support array type tags, each element in the array can easily be represented with the array data types in Ignition. 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.

    New in 8.1.33
    The array tag type will now accept and coerce JSON array types, allowing methods such as jsonGet.

    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

    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:

    • Float
    • Short
    • Long
    • Date
    • Integer
    • Boolean
    • String
    • Color
    • Double
    • Timestamp
    • New in 8.1.20
      Byte Arrays

    Dataset Tag Example

    The following example will create a dataset memory tag and display the contents in a Table component.

    1. Create a new Memory Tag. Name it Dataset, and change the data type to Dataset. The Dataset will be empty by default.
    2. Click the Edit icon next to Value. The Value screen is displayed. For this example, we created a simple dataset with four columns and five rows.
    3. Click the Add Column icon. Name the first column City and set type to be String.
    4. Click Add Column.

    5. Repeat adding columns as follows:
      • Column Name: Population Type: Integer
      • Column Name: TimeZone Type: String
      • Column Name: GMTOffset Type: Integer
    6. Click the Add Row icon. Add the row information as follows:

      New York8368710EST-5
      Los Angeles3833995PST-8
    7. Click the Commit button.
    8. Click OK to save the tag.

    The tag will now contain rows, columns, and values based on the configurations you made earlier in this example. Now you have a tag with a dataset value that can be bound to by components in Vision and Perspective.

    Document Type

    The document type allows a tag to have a JSON document as a value. Note that the Tag History system does not support tags with a document type.


    Most OPC device drivers do not support the document data type. This type works best when used on query tags or memory tags.

    New in 8.1.27
    The document tag type now supports writing to OPC tags containing DocumentArray values. 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.

    New in 8.1.32
    The document tag type will now accept and coerce PyDictionary types.