# UDT OPC Path in group paste **URL:** \ **Category:** Ignition\ **Created:** [December 20, 2025, 9:12pm UTC](https://forum.inductiveautomation.com/t/udt-opc-path-in-group-paste/112933 "2025-12-20T21:12:39Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Jason\_Crockett](https://avatars.discourse-cdn.com/v4/letter/j/e99b99/32.png) [@Jason\_Crockett](https://forum.inductiveautomation.com/u/Jason_Crockett)\ **Post date:** [December 20, 2025, 9:12pm UTC](https://forum.inductiveautomation.com/t/udt-opc-path-in-group-paste/112933/1 "2025-12-20T21:12:39Z")
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](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/c/fc7cfeb1a7f812e2540bf594a15d695edbb2190c.jpeg) ![Constants](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/5/a5dad4460bf02f0ab9f1ed1723a396294d33db86.jpeg) ![UDTTagPath](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/c/3cc5907d25175594a8948a93145ac84e1aa41e0c.jpeg) 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](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/7/a7527ebf5d75e25ed0c09e47a6fcc3423115f210.jpeg) ![TagEditor](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/f/5feb40e4d21e542abf69cfe348aa9d4b857a2951.jpeg) ![TagTree](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/4/74271f815a7745d463d665ad226e3cd84216ca18.jpeg) 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](https://forum.inductiveautomation.com/t/udt-opc-path-issues/26493) ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [December 21, 2025, 1:53am UTC](https://forum.inductiveautomation.com/t/udt-opc-path-in-group-paste/112933/2 "2025-12-21T01:53:01Z")
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 ---
**Author:** ![Chris\_Bingham](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@Chris\_Bingham](https://forum.inductiveautomation.com/u/Chris_Bingham)\ **Post date:** [December 22, 2025, 3:50pm UTC](https://forum.inductiveautomation.com/t/udt-opc-path-in-group-paste/112933/3 "2025-12-22T15:50:18Z")
> [@Jason\_Crockett](#): > > What am I missing when I paste the path into a group of tags? 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](https://Exporting%20and%20Importing%20Tags%20-%20Tag%20File%20Formats) One option to help keep items consistent across similar UDTs is [UDT Inheritance](https://www.docs.inductiveautomation.com/docs/8.1/platform/tags/user-defined-types-udts/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. ---
**Author:** ![Jason\_Crockett](https://avatars.discourse-cdn.com/v4/letter/j/e99b99/32.png) [@Jason\_Crockett](https://forum.inductiveautomation.com/u/Jason_Crockett)\ **Post date:** [December 22, 2025, 4:21pm UTC](https://forum.inductiveautomation.com/t/udt-opc-path-in-group-paste/112933/4 "2025-12-22T16:21:15Z")
This is very helpful. Thank you!