# Nested UDT Parameters reading its own parameters before going up a level

**URL:** <https://forum.inductiveautomation.com/t/nested-udt-parameters-reading-its-own-parameters-before-going-up-a-level/41612>\
**Category:** Ignition Early Access\
**Created:** [December 17, 2020, 2:33pm UTC](https://forum.inductiveautomation.com/t/nested-udt-parameters-reading-its-own-parameters-before-going-up-a-level/41612 "2020-12-17T14:33:13Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Walt](https://avatars.discourse-cdn.com/v4/letter/w/71e660/32.png) [@Walt](https://forum.inductiveautomation.com/u/Walt)\
**Post date:** [December 17, 2020, 2:33pm UTC](https://forum.inductiveautomation.com/t/nested-udt-parameters-reading-its-own-parameters-before-going-up-a-level/41612/1 "2020-12-17T14:33:13Z")

</div>

I would say this was broken somewhere after 8.0.10. We didn’t notice it until we started using 8.1. Luckily we haven’t pushed 8.1 into production yet or this would have broken most of UDT based tags.

The problem comes in when you try to set one of the parameters on the nested UDT to one of the parameters for the next level up UDT. If parameters on both UDTs have the same name it seems to find the parameter value of its own parameter rather than looking up a level. This example is kind of messy as I was tearing things up to find out what was going on. But you’ll see the ThisTag parameter in MotorStarter\_Alarm should be an empty string.

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

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/a/7ab75386eebd72f255515e68a57af182113dd1d0.png)