# Popup parameters passing - any difference when using vision template repeater

**URL:** <https://forum.inductiveautomation.com/t/popup-parameters-passing-any-difference-when-using-vision-template-repeater/75816>\
**Category:** Ignition\
**Tags:** ignition81, vision\
**Created:** [July 2, 2023, 8:23am UTC](https://forum.inductiveautomation.com/t/popup-parameters-passing-any-difference-when-using-vision-template-repeater/75816 "2023-07-02T08:23:58Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![hewking32](https://avatars.discourse-cdn.com/v4/letter/h/b5ac83/32.png) [@hewking32](https://forum.inductiveautomation.com/u/hewking32)\
**Post date:** [July 2, 2023, 8:23am UTC](https://forum.inductiveautomation.com/t/popup-parameters-passing-any-difference-when-using-vision-template-repeater/75816/1 "2023-07-02T08:23:58Z")

</div>

Hi  
Maybe its because Sunday and i am bit fuzzy but i am struggling to make a popup parameters work when there is template repeater.  
I got basics covered:  
1 There is on click action behind template to open popup with passing UDT parameter configured  
2 popup root container does have matching custom parameter of UDT type  
When i click on the any instance inside template repeater i got messages "Cannot assign orphaned UDT instance to a component property: Root Container"

I have no problem passing integer parameter via popup but UDT does not work.  
Also passing UDT without template repeater did work in the past.

Any suggestion how to troubleshoot it?

---

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [July 2, 2023, 10:11am UTC](https://forum.inductiveautomation.com/t/popup-parameters-passing-any-difference-when-using-vision-template-repeater/75816/2 "2023-07-02T10:11:21Z")

</div>

No can do. You're simply unable to pass udt types to a popup, which is one of the many reasons not to use UDTType parameters at all. Just pass the tagpath to the UDT instance instead to the popup (and to the Template too)

---

<div class="post-metadata">

**Author:** ![hewking32](https://avatars.discourse-cdn.com/v4/letter/h/b5ac83/32.png) [@hewking32](https://forum.inductiveautomation.com/u/hewking32)\
**Post date:** [July 2, 2023, 11:12am UTC](https://forum.inductiveautomation.com/t/popup-parameters-passing-any-difference-when-using-vision-template-repeater/75816/3 "2023-07-02T11:12:39Z")

</div>

> [@nminchin](#):
>
> You're simply unable to pass udt types to a popup

hm i passed udt to popup in the past without issues. Any chance you elaborate on this?

---

<div class="post-metadata">

**Author:** ![hewking32](https://avatars.discourse-cdn.com/v4/letter/h/b5ac83/32.png) [@hewking32](https://forum.inductiveautomation.com/u/hewking32)\
**Post date:** [July 2, 2023, 11:15am UTC](https://forum.inductiveautomation.com/t/popup-parameters-passing-any-difference-when-using-vision-template-repeater/75816/4 "2023-07-02T11:15:16Z")

</div>

> [@nminchin](#):
>
> Just pass the tagpath to the UDT instance instead to the popup (and to the Template too)

how is this supposed to work in practice. I have template repeater with instances inside?  
do i need to create custom property on template repeater? Any chance for simplest example please?

---

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [July 2, 2023, 11:30am UTC](https://forum.inductiveautomation.com/t/popup-parameters-passing-any-difference-when-using-vision-template-repeater/75816/5 "2023-07-02T11:30:21Z")

</div>

Your template params dataset should be a list of the tag paths to the UDT instances, and the column name should match the tag path parameter in your templates. Eg `deviceTagPath`

---

<div class="post-metadata">

**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:** [July 2, 2023, 1:43pm UTC](https://forum.inductiveautomation.com/t/popup-parameters-passing-any-difference-when-using-vision-template-repeater/75816/6 "2023-07-02T13:43:24Z")

</div>

See also this recent long discussion of UDT properties and their pitfalls:

> [@\[IGN-8148\]Is it possible to use a whole tag as a custom property / drop target for a template, or to reference the source tag of a non-UDT drop target?](https://forum.inductiveautomation.com/t/is-it-possible-to-use-a-whole-tag-as-a-custom-property-drop-target-for-a-template-or-to-reference-the-source-tag-of-a-non-udt-drop-target/74203):
>
> Lets say I want to make an indicator for a boolean tag that uses the tag's name as the text in the indicator, and I want this to be a template so that I can make a page that is all the statuses of all of the booleans that I am interested in monitoring. What I thought I could do was make a template that is just contains a slightly dressed Multi State Indicator: slimming the style to take just 0 or 1 as values and binding text in the indicator to be the Name property of the dropped-in tag. I thou…

You should be breaking bad habits before they get too ingrained.
