# Make a Vision Template with a droppable Tag that you can reference multiple properties inside **URL:** \ **Category:** Ignition\ **Tags:** ignition81, vision\ **Created:** [September 19, 2022, 7:55pm UTC](https://forum.inductiveautomation.com/t/make-a-vision-template-with-a-droppable-tag-that-you-can-reference-multiple-properties-inside/64249 "2022-09-19T19:55:44Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![BRAD\_DAVIS](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/brad_davis/32/35392_2.png) [@BRAD\_DAVIS](https://forum.inductiveautomation.com/u/BRAD_DAVIS)\ **Post date:** [September 19, 2022, 7:55pm UTC](https://forum.inductiveautomation.com/t/make-a-vision-template-with-a-droppable-tag-that-you-can-reference-multiple-properties-inside/64249/1 "2022-09-19T19:55:44Z")
I am wondering if its possible to make a vision template with the following: - Droppable customizer where i can map a tag - Make it so sub components can take different portions of the mapped tag (one item references its value and the other references its name What I am trying to achieve is that i have a device control popup screen and i want to show the alarms that are associated with that device and whether they are currently in alarm or not. I have done this manually, but it is error prone as it involves a lot of manual clicking. What my ideal situation would be (though i assume igntion currently doesnt support this behaviour) is the ability to make a customizer that links to a tag in its entirely, then allows me to reference its properties within the template. This or the ability to make a table and be able to quickly drag tags to it to allow me to construct a map of all the alarm tags that apply to said device and view each of the alarms name and value ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [September 19, 2022, 8:02pm UTC](https://forum.inductiveautomation.com/t/make-a-vision-template-with-a-droppable-tag-that-you-can-reference-multiple-properties-inside/64249/2 "2022-09-19T20:02:46Z")
It’s not quite as easy of an experience, but I’d recommend a simple string parameter on the template that forms the ‘base’ tag path. Then it’s easy to build indirection off of that base path in other bindings/scripts/etc within the template. It’s also going to be more performant/less of a bottleneck down the road, too. ---
**Author:** ![BRAD\_DAVIS](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/brad_davis/32/35392_2.png) [@BRAD\_DAVIS](https://forum.inductiveautomation.com/u/BRAD_DAVIS)\ **Post date:** [September 20, 2022, 2:07pm UTC](https://forum.inductiveautomation.com/t/make-a-vision-template-with-a-droppable-tag-that-you-can-reference-multiple-properties-inside/64249/3 "2022-09-20T14:07:57Z")
Not ideal but i can make that work yeah. I was able to make a big template for the whole screen and incorperate all of the tags i needed to bind in it with this method. Its a shame you cant reference a whole tag as a customizer and then just get to take parts of it as needed though. ---
**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:** [September 20, 2022, 2:13pm UTC](https://forum.inductiveautomation.com/t/make-a-vision-template-with-a-droppable-tag-that-you-can-reference-multiple-properties-inside/64249/4 "2022-09-20T14:13:32Z")
> [@BRAD\_DAVIS](#): > > Not ideal but i can make that work yeah. You may change your mind as you get used to the idea. Most Ignition experts use it everywhere.