# Popups In Perspective **URL:** \ **Category:** Ignition\ **Tags:** perspective, ignition81\ **Created:** [October 5, 2021, 11:11pm UTC](https://forum.inductiveautomation.com/t/popups-in-perspective/51640 "2021-10-05T23:11:35Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![zacht](https://avatars.discourse-cdn.com/v4/letter/z/ea5d25/32.png) [@zacht](https://forum.inductiveautomation.com/u/zacht)\ **Post date:** [October 5, 2021, 11:31pm UTC](https://forum.inductiveautomation.com/t/popups-in-perspective/51640/2 "2021-10-05T23:31:02Z")
I don't know the answer to your actual question, but I know there are several users of the forum, myself included, who prefer to send the tagpath of a UDT as a string instead of the UDT instance. In this method you use indirect tag bindings (which can be bidirectional) instead of property bindings to the UDT parameter. More info in this post. > [@UDT parameter vs Indirect Binding in Template development](https://forum.inductiveautomation.com/t/udt-parameter-vs-indirect-binding-in-template-development/18197): > > In development of template for udt, it’s possible to use two different way to pass value from a instance of udt to template. You can add a parameter and select udt as type, or you can add string parameter to use to pass tag path. I would yours opinion on what is better to use in development of template UDT parameters or indirect tag. I drawn up a list with pro e cons of both UDT Parameter: Pro: one whole object with all subtags; Drag&Drop Subtags accessible as property simplicity to comb… --- _[View the full topic](https://forum.inductiveautomation.com/t/popups-in-perspective/51640)._