# Nested UDT parameter passing BUG

**URL:** <https://forum.inductiveautomation.com/t/nested-udt-parameter-passing-bug/36905>\
**Category:** Ignition Early Access\
**Tags:** ignition80, vision\
**Created:** [July 21, 2020, 4:16pm UTC](https://forum.inductiveautomation.com/t/nested-udt-parameter-passing-bug/36905 "2020-07-21T16:16:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dmalec](https://avatars.discourse-cdn.com/v4/letter/d/e47774/32.png) [@dmalec](https://forum.inductiveautomation.com/u/dmalec)\
**Post date:** [July 21, 2020, 4:16pm UTC](https://forum.inductiveautomation.com/t/nested-udt-parameter-passing-bug/36905/1 "2020-07-21T16:16:55Z")

</div>

Hello, i have found a bug where parameter passing other parameters in the base datatype results in null/issues but when the same parameter is passed in manually it works

**Broken step 1)** - structure layout

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/b/eb8fa0517cccca0f8985f7278bf25649b8626366.png)

**Broken step 2)** - pre-filled out parameters

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/3/538c7fcbf628936568c0c6b4ef060187482e5026.png)

**Broken step 3)** - blank UDT instance created  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/2/22ba2ff8849dba01e4df204d40faa5731d6a310e.png)

**Broken step 4)** - blank UDT parameters filled in  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/d/cd79442dbec72bfdb7362cba4351f28eaf1f14cf.png)

**Broken step 5)** -expanding alarm parameters shows null/bad values  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/5/156f933eaf3170348c5994e820e34b2be2cb8e3f.png)

**Working step 1)** -deleted prefilled parameter values

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

**Working step 2)** -Same as broken step 3/4

**Working step 3)** - Filling out parameters manually on the instance versus the definition

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

**Working step 4)** Green light confirms overwridden  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/b/5b1a15cfe9379deb5957889cfc1da069ff332e4a.png)

**Working step 5)** Overwritten variables worked  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/c/9c7828807b190ba4fd1e1dbf40aefbf426fdcb8c.png)

**General picture** - parameters im sending into the alarm UDTs are found on the base UDT object

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

**Semi-working step 1)** - In the new instance creation window, if i prefill the parameters versus after i make the tag

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/6/f6f322b05da3ccba1215a49ea46c16994213248b.png)

**Semi-working step 2)** - The values fill out properly however the alarm message doesnt link right  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/9/d9b62b35479c2dbc597884987f3c6438ef32923e.png)

**Semi-working step 3)** - The Label is the ALARM\_MESSAGE and is basically treated as null which is why Alarm is displayed (name of the alarm)

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

**Semi-working step 4)** - This is the alarms configuration

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/e/feb3e3a2d1579f28ed8fa616d1d32e1e082dbcaa.png)

**General** - At the moment, it appears the only way to get it working properly is to make a blank UDT and fill in the parameters after creation, because the semi-working only gets the address and PLC part right, but the alarm message for some reason returns null, but its not ideal due to manual work versus the parameters being properly passed through

---

<div class="post-metadata">

**Author:** ![dmalec](https://avatars.discourse-cdn.com/v4/letter/d/e47774/32.png) [@dmalec](https://forum.inductiveautomation.com/u/dmalec)\
**Post date:** [July 21, 2020, 4:18pm UTC](https://forum.inductiveautomation.com/t/nested-udt-parameter-passing-bug/36905/2 "2020-07-21T16:18:25Z")

</div>

also here are my ignition versions  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/c/4cb779989c5c59fb9a6b9c914f86dd5b270ce1c9.png)

---

<div class="post-metadata">

**Author:** ![mrojas](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mrojas/32/6394_2.png) [@mrojas](https://forum.inductiveautomation.com/u/mrojas)\
**Post date:** [July 24, 2020, 4:17pm UTC](https://forum.inductiveautomation.com/t/nested-udt-parameter-passing-bug/36905/3 "2020-07-24T16:17:00Z")

</div>

We’ve addressed a number of issues related to UDT Parameters recently. Upgrading to 8.0.15 should fix what you were seeing.