# \[Question\]How to access individual tags inside a UDT from OMRON NX PLC OPC server? **URL:** \ **Category:** Ignition\ **Created:** [September 13, 2019, 5:47am UTC](https://forum.inductiveautomation.com/t/question-how-to-access-individual-tags-inside-a-udt-from-omron-nx-plc-opc-server/28236 "2019-09-13T05:47:42Z")\ **Posts on this page:** 1\ **Showing post:** 4
**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:** [September 13, 2019, 12:57pm UTC](https://forum.inductiveautomation.com/t/question-how-to-access-individual-tags-inside-a-udt-from-omron-nx-plc-opc-server/28236/4 "2019-09-13T12:57:47Z")
> [@rahul.ray](#): > > the tag browser, the data type is “Document” Well, that means you can use jsonGet to read out individual elements: > [@OPC UA struct data type?](http://forum.inductiveautomation.com/t/opc-ua-struct-data-type/26905/2): > > You can take advantage of reading whole structs in OPC UA servers as of Ignition 7.9.12 and 8.0.0. When you bring the tag in you’ll notice Ignition presents a JSON value. The strategy here is a little involved but it works. For each of the UDTs you’ll be subscribing to in the PLC you make a corresponding UDT in Ignition. It should have a “Source” OPC tag member that will correspond to the Node with the struct value in the server and as a result have a JSON value in Ignition. Then for each memb… --- _[View the full topic](https://forum.inductiveautomation.com/t/question-how-to-access-individual-tags-inside-a-udt-from-omron-nx-plc-opc-server/28236)._