UDT OPC Path in group paste

Ignition
1

Version: 8.1.49 (b2025081208)

I am creating my first UDT. So bare with me on my terminology and such. The UDT I am creating are for Totaflow meters. I have 3 different configs on the meters so I am trying to create 3 unique UDT’s for their respective setup.

I believe I have created the first UDT correctly that I will use for a Fuel Meter using parameters. When I create a new Data Type Instance using the UDT, it brings in the new device with the EU’s and history that I setup.

My issue is when I create a new UDT from an existing device, I want to use some of the same OPC data path I used in EFM_TF_Fuel_Recycle UDT. The devices are similar but they are slightly different in naming, EU’s and history needs. When I am modifying the tagpaths during this process, if I paste the path into each tag individually, the path will italicize. If I select a group of tags and paste the OPC data path, the path does not italicize or work when I open the individual tag to verify the path works. I have to delete the OPC data path in the tag, apply, then paste and apply for the OPC data path to take effect.

Below, Fuel_Recycle is the first UDT and working. The Flare UDT, I copied the tag path and pasted it in as a group. This is to show they match. I could not figure out to not have to type [Diagnostics] or Constants. If you can help with that also….hehehe

EditBinding
EditBinding921×454 78.7 KB

Constants
Constants920×454 79.8 KB

UDTTagPath
UDTTagPath1087×731 193 KB

As you can see the OPC Item Path did not italicize when I opened the tag in the UDT. Also when I look at the device created in the tag list, the path did not italicize.

GroupPaste
GroupPaste1109×789 148 KB

TagEditor
TagEditor1279×1157 239 KB

TagTree
TagTree1149×807 142 KB

When I paste the OPC data path into individual tags within the UDT editor, then save. The live tags work without issue.

What am I missing when I paste the path into a group of tags?

I found this post about the issue back in 2024 but didn’t see any resolution to it.

UDT OPC Path Issues - Ignition Early Access - Inductive Automation Forum

2

Looks like a bug to me. The issue is almost guaranteed to be that when you paste it for multiple, it’s not applying it as a binding but just as static text. If you copy the json of the UDT definition and look at it in a text editor you’ll see the difference

2 Likes
3

As @nminchin alludes, pasting to a property field directly does not always apply as a binding. In the early screenshots of your post, you show screenshots of the property binding editor, whereby you can have confidence that your curly braces will be evaluated as a binding, and not as a literal string. The binding editor is not available for bulk edits, so you're stuck with pasting the would-be binding as a literal string.

For editing OR building in bulk, I recommend exporting your tags and modifying the JSON directly there (via search/replace, or a separate / custom tool). Here's some example import files of varying supported file types from Ignition 8.1 docs:
https://www.docs.inductiveautomation.com/docs/8.1/platform/tags/exporting-and-importing-tags#tag-file-formats

One option to help keep items consistent across similar UDTs is UDT Inheritance. Here, you build a 'base' UDT, which can be used as a parent data type for the other UDTs. You can then add new tags in the children UDTs or override any properties that were assigned in the parent.

2 Likes
4

This is very helpful.

Thank you!