# OPC UA ExtensionObject not browsable 8.3 **URL:** \ **Category:** Ignition\ **Tags:** opcua, ignition83\ **Created:** [October 30, 2025, 10:46am UTC](https://forum.inductiveautomation.com/t/opc-ua-extensionobject-not-browsable-8-3/111814 "2025-10-30T10:46:44Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [October 30, 2025, 1:10pm UTC](https://forum.inductiveautomation.com/t/opc-ua-extensionobject-not-browsable-8-3/111814/4 "2025-10-30T13:10:30Z")
Most people create Ignition UDTs corresponding to each structured type that contain the derived tags with the JSON expressions. > [@OPC UA struct data type?](https://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… There's an annoying amount of overhead in working with these types right now. It's not something we're actively working on, but it's something we're actively _thinking_ about, along with other possible OPC UA integration improvements for the future. --- _[View the full topic](https://forum.inductiveautomation.com/t/opc-ua-extensionobject-not-browsable-8-3/111814)._