# How to map OPC UDT to Ignition template

**URL:** <https://forum.inductiveautomation.com/t/how-to-map-opc-udt-to-ignition-template/27269>\
**Category:** Ignition\
**Created:** [August 8, 2019, 2:52pm UTC](https://forum.inductiveautomation.com/t/how-to-map-opc-udt-to-ignition-template/27269 "2019-08-08T14:52:42Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**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:** [August 8, 2019, 3:12pm UTC](https://forum.inductiveautomation.com/t/how-to-map-opc-udt-to-ignition-template/27269/2 "2019-08-08T15:12:18Z")

</div>

It might be easier if you turn these into Ignition UDTs using the strategy outlined in this post: [OPC UA struct data type?](http://forum.inductiveautomation.com/t/opc-ua-struct-data-type/26905/2?u=kevin.herron)

You might also be able to skip that and use `jsonGet` and `jsonSet` from your template bindings. But it wouldn’t happen automatically.

---

_[View the full topic](https://forum.inductiveautomation.com/t/how-to-map-opc-udt-to-ignition-template/27269)._