# Dynamically Binding to Multiple Tags

**URL:** <https://forum.inductiveautomation.com/t/dynamically-binding-to-multiple-tags/78244>\
**Category:** Ignition\
**Tags:** vision\
**Created:** [August 22, 2023, 4:16pm UTC](https://forum.inductiveautomation.com/t/dynamically-binding-to-multiple-tags/78244 "2023-08-22T16:16:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![John\_Maldonado](https://avatars.discourse-cdn.com/v4/letter/j/c68b51/32.png) [@John\_Maldonado](https://forum.inductiveautomation.com/u/John_Maldonado)\
**Post date:** [August 22, 2023, 4:16pm UTC](https://forum.inductiveautomation.com/t/dynamically-binding-to-multiple-tags/78244/1 "2023-08-22T16:16:24Z")

</div>

Hello,

I'm working on a vision template where I'm needing to bind to an unkown number of tags.

Essentially, on the template I'll have an ID custom prop which I can use to query a database.  
The query will produce a number of tag paths to some boolean tags for which I need to check the value of each and check if any of the values are true. That true or false will be stored in a custom prop to hide or show a component.

I can't think of a way to do this with bindings but I thought I would ask.

My other thought was to use a timer component with a script that polls regularly, though I know that's generally seen as a bad practice.

Any ideas?

---

<div class="post-metadata">

**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\
**Post date:** [August 22, 2023, 4:26pm UTC](https://forum.inductiveautomation.com/t/dynamically-binding-to-multiple-tags/78244/2 "2023-08-22T16:26:42Z")

</div>

Maybe try this module from @pturmel

> [@Automation Professionals' Integration Toolkit Module](https://forum.inductiveautomation.com/t/automation-professionals-simulation-aids-v2/74934/63):
>
> Annnnnnd... another new feature: the tags() expression function. Note the plural. It takes a list of tag paths, or a dataset with tag paths in the first column. It defaults to operating in subscription mode, without an initial read, so the first execution will always yield nulls. Quickly replaced with proper values as the subscriptions report in. If the list changes between executions, only the changed tag paths will report a null at that point. It can be set to not use subscriptions, in …