# OPC path for nested UDT

**URL:** <https://forum.inductiveautomation.com/t/opc-path-for-nested-udt/89879>\
**Category:** Maker\
**Tags:** ignition81, perspective\
**Created:** [May 3, 2024, 9:13am UTC](https://forum.inductiveautomation.com/t/opc-path-for-nested-udt/89879 "2024-05-03T09:13:32Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vidar\_Hetlelid](https://avatars.discourse-cdn.com/v4/letter/v/dfb087/32.png) [@Vidar\_Hetlelid](https://forum.inductiveautomation.com/u/Vidar_Hetlelid)\
**Post date:** [May 3, 2024, 9:13am UTC](https://forum.inductiveautomation.com/t/opc-path-for-nested-udt/89879/1 "2024-05-03T09:13:32Z")

</div>

Hi there,

I'm trying to make nested UDT tag for OPCUA. I have made it like this, which is identicly as how its provided from the PLC via OPCUA.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/1/31fc99f47d98e02872c76925bcdfe68000b3e148.png)

Problem is that every tag is binded to its own OPCUA tag path. When I add an instance of "kettle", i have to adjust the OPCUA tag for each of them. How can this be done effectively?

I want to add many instances, and I was hoping I could use drag and drop while browsing opc tags, and that the opc path was updated. Is that possible?

I assume the way to go is use the OPCUA path of "kettle" and adjust the path for each tag below based on its name, but I dont get how that can be accieved.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/c/0c8f3a4394371b15e14162a80db81f586cb8172a.png)

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [May 3, 2024, 11:20am UTC](https://forum.inductiveautomation.com/t/opc-path-for-nested-udt/89879/2 "2024-05-03T11:20:58Z")

</div>

That's what UDT parameters are for. Create a parameter that represents the "folder" of the OPC Item Path. Have all nested OPC tags use that with a suffix to address the real target.

---

<div class="post-metadata">

**Author:** ![Vidar\_Hetlelid](https://avatars.discourse-cdn.com/v4/letter/v/dfb087/32.png) [@Vidar\_Hetlelid](https://forum.inductiveautomation.com/u/Vidar_Hetlelid)\
**Post date:** [May 3, 2024, 10:34pm UTC](https://forum.inductiveautomation.com/t/opc-path-for-nested-udt/89879/3 "2024-05-03T22:34:37Z")

</div>

Thanks. I have tried to accomplish that, but not sure how I should approch. Any chance you can show me an example?

---

<div class="post-metadata">

**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\
**Post date:** [May 3, 2024, 10:46pm UTC](https://forum.inductiveautomation.com/t/opc-path-for-nested-udt/89879/4 "2024-05-03T22:46:11Z")

</div>

While I could just show you, I think it's better if you go learn it from the videos here:

> **[Inductive University Course List - Learn Ignition Free](https://inductiveuniversity.com/courses/ignition/tags-in-ignition/8.1)**
>
> Learn the fundamentals and advanced features of Ignition while earning your IU credential

Especially watch the ones based on UDTs and parameters in UDTs.