You can import Tags to a individual folder or under the Tags tab. To import Tags under the Tags tab, you can click the Tags tab or the empty space at the bottom of the Tag Browser below all your Tags. When importing Tags, you need to tell Ignition how to handle duplicate Tags. If any of the Tags being imported already exist in the folder you specify, Ignition can abort the import, overwrite the Tags, rename them, ignore them, or merge them. This is called a collision policy.
Collision Policy Options Table
Aborts the import if duplicate Tags are found.
Overwrites any Tags in the folder that have the same name as Tags being imported. Note this a complete overwrite of the Tag.
Renames any duplicate Tags.
Ignores duplicate Tags and imports only those that are unique.
Overwrites the Tag with the exception of any properties that aren't defined in the import folder. Those properties will be merged.
- On the Tag Browser toolbar, click the Import icon.
- Specify the folder you want to import your Tags from, and choose a previously exported file either .json, .xml, or .csv file type.
- Choose a Collision Policy, which indicates how Ignition will deal with duplicate Tags.
- Click Open to import the Tags.
- The Tags now appear in the Tag Browser in the folder you indicated for the import.
Tag File Formats
Tags can be imported from CSV, JSON, and XML. Tags can only be exported in XML or JSON. There are many configuration settings for Tags than what is displayed in a JSON or XML export file. The Tag export feature only exports the configuration properties that have been edited in at least one of the Tags in the selected export folder. Therefore, to ensure the desired configuration setting is available in the export file, at least one Tag within the selected export folder must have that configuration property changed.
Legacy Ignition systems exported Tags as a CSV formatted file. This functionality was deprecated in Ignition 7.6.0.
Modern Gateways can not export Tags to a CSV file, but they can still import Tags from this legacy CSV format. This is offered as a means to support those migrating to Ignition from a third-party system. Note that importing Tags from the CSV format in this manner will not create any alarms on the imported Tags.
Below is an example of the legacy CSV format, which contains a couple of different Tag types, purely for demonstrative purposes. It contains:
- An OPC Tag
- A Folder
- An OPC Tag located in a folder
- A Derived Tag
- An Expression Tag
- A Memory Tag
- A Query Tag
Property Values in the CSV Import
The following table shows the configuration property names and values contained in legacy CSV Tag import files. Tags were overhauled in Ignition 8.0, so the properties listed here are not the same as Tags export from an Ignition 8.0+ system. For modern tag properties, see the Tag Properties and Tag Property Enum Reference pages.
Values (if applicable)
|Value||The value of the Tag, dependent on the data type.|
0 - Int1
0 - OPC Tag
Determines the type of the Tag.
A value of one is a "DB Tag", which is either a Memory Tag, Query Tag, or Expression Tag, depending on the value of the ExpressionType field.
0 - None
|Used in conjunction when the TagType is set to 1 (DB Tag), otherwise this field is ignored.|
|AccessRights||Int||0 - Read Only|
1 - Read/Write
2 - Custom
|If custom, will be defined by a Permissions Tag.|
|OPCWriteBackServer||String||Write back target for expression Tags.|
|ScaleMode||Int||0 - Off|
1 - Linear
2 - Square Root
3 - Exponential Filter
|ScaleFactor||Float||For exponential filter.|
|RawLow||Float||Defines scale range.|
0 - None
0 - Absolute
0 - None
|DriverName||String||Used for external Tags.|
|ScanClass||String||The export will only include the name of the Scanclass, not the configuration of the Scanclass itself. A Scanclass with the same name needs to already exist on the Gateway that the Tags are being imported to, prior to importing them.|
|PrimaryHistoryProvider||String||The history provider to use if storing history.|
0 - Absolute
0 - Discrete
How values are interpolated. 2 exists for backwards compatibility (and is equivalent to 1), but only 0 or 3 should be used in the future.
0 - System
0 - Unlimited
|HistoryMaxAge||Int||Max cycles between storage.|
The path to the parent UDT type. Used by sub-types and instances.
In this example, we exported all Tags in our Tag Browser (with the exception of the Motor UDT). The following Tags were exported.
- C Temp - Expression Tag with an Alarm
- F Temp - Memory Tag with History Settings
- OPC - OPC Tag
- Motor 1 - UDT Instance
The following exported Tag file is in JSON format. As you browse through the JSON file, you will see the Tag properties and configuration settings for each of the four Tags listed above.
In this example, we exported the same four Tags from our Tag Browser, that were also used in the JSON example, in XML format. As you browse through the XML file, you will see the Tag properties and configuration settings for each of the same four Tags.