# Preventing Conflicts in Power Table Across Multiple Ignition Vision Clients **URL:** \ **Category:** Ignition\ **Tags:** vision\ **Created:** [November 14, 2024, 3:38pm UTC](https://forum.inductiveautomation.com/t/preventing-conflicts-in-power-table-across-multiple-ignition-vision-clients/98618 "2024-11-14T15:38:46Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![S\_C](https://avatars.discourse-cdn.com/v4/letter/s/9dc877/32.png) [@S\_C](https://forum.inductiveautomation.com/u/S_C)\ **Post date:** [November 14, 2024, 3:38pm UTC](https://forum.inductiveautomation.com/t/preventing-conflicts-in-power-table-across-multiple-ignition-vision-clients/98618/1 "2024-11-14T15:38:46Z")
I am using a Power table to display test results from a database. I have the power table linked to a query tag. The query itself is linked to multiple other tags to filter the data accordingly. The problem I am having is when one client window makes a change to the filters and updates the table, it updates other open windows too which makes sense because the tags just got updated. How do I solve this problem where any changes on one window doesn't transfer to other client windows? ---
**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\ **Post date:** [November 14, 2024, 3:46pm UTC](https://forum.inductiveautomation.com/t/preventing-conflicts-in-power-table-across-multiple-ignition-vision-clients/98618/2 "2024-11-14T15:46:24Z")
It seems to me that the current behaviour is the correct behaviour. Why do the other clients need to display stale data? ---
**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:** [November 14, 2024, 3:47pm UTC](https://forum.inductiveautomation.com/t/preventing-conflicts-in-power-table-across-multiple-ignition-vision-clients/98618/3 "2024-11-14T15:47:45Z")
When you need independence amount multiple clients, don't use tags. Just use custom properties in your UI. If you need shared information across multiple **windows** , you might use Vision Client Tags. ---
**Author:** ![S\_C](https://avatars.discourse-cdn.com/v4/letter/s/9dc877/32.png) [@S\_C](https://forum.inductiveautomation.com/u/S_C)\ **Post date:** [November 14, 2024, 4:13pm UTC](https://forum.inductiveautomation.com/t/preventing-conflicts-in-power-table-across-multiple-ignition-vision-clients/98618/4 "2024-11-14T16:13:25Z")
It is a correct, but I want different users to be able to filter the data according to their needs and see it. For example, two different users might want to see data for two different stations and so on. ---
**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:** [November 14, 2024, 4:14pm UTC](https://forum.inductiveautomation.com/t/preventing-conflicts-in-power-table-across-multiple-ignition-vision-clients/98618/5 "2024-11-14T16:14:11Z")
Sure...but why tags at all, then? The whole point of tags (excluding Vision Client Tags, which are a special unicorn) is that they're globally scoped resources. ---
**Author:** ![S\_C](https://avatars.discourse-cdn.com/v4/letter/s/9dc877/32.png) [@S\_C](https://forum.inductiveautomation.com/u/S_C)\ **Post date:** [November 14, 2024, 4:15pm UTC](https://forum.inductiveautomation.com/t/preventing-conflicts-in-power-table-across-multiple-ignition-vision-clients/98618/6 "2024-11-14T16:15:05Z")
Can I tie the component's value directly to the query? ---
**Author:** ![S\_C](https://avatars.discourse-cdn.com/v4/letter/s/9dc877/32.png) [@S\_C](https://forum.inductiveautomation.com/u/S_C)\ **Post date:** [November 14, 2024, 4:19pm UTC](https://forum.inductiveautomation.com/t/preventing-conflicts-in-power-table-across-multiple-ignition-vision-clients/98618/7 "2024-11-14T16:19:22Z")
I realize tags aren't way to go, but I needed to store the filters data and transfer it to the query, how would you recommend doing it? ---
**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:** [November 14, 2024, 4:24pm UTC](https://forum.inductiveautomation.com/t/preventing-conflicts-in-power-table-across-multiple-ignition-vision-clients/98618/8 "2024-11-14T16:24:01Z")
Use a named query binding (preferred): > **[Named Query Binding Video at Inductive University](https://inductiveuniversity.com/video/named-query-binding/8.1)** > > Learn how to setup a Named Query binding. The Named Query binding takes an existing Named Query and uses it in a binding. Or, if you aren't able to, use a SQL query binding, but you'll have to enable a less-safe option in your project's permissions: > **[SQL Query Binding - Dynamic Filters Video at Inductive University](https://inductiveuniversity.com/videos/sql-query-binding-dynamic-filters/8.1)** > > Learn how to make your SQL queries dynamic by including property values and Tag values in the query. ---
**Author:** ![leonardo.godoi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/leonardo.godoi/32/27178_2.png) [@leonardo.godoi](https://forum.inductiveautomation.com/u/leonardo.godoi)\ **Post date:** [November 14, 2024, 4:42pm UTC](https://forum.inductiveautomation.com/t/preventing-conflicts-in-power-table-across-multiple-ignition-vision-clients/98618/9 "2024-11-14T16:42:53Z")
> [@S\_C](#): > > store the filters data and transfer it to the query Do you actually need to store the filter's data or you just need help to find a way to retrieve them when they're not a tag? What do you need to happen when you open your window? A)See the latest selected filter parameters independently of which client chose them? B)See the latest filter values that only this particular client chose? C)Or is it fine for you to open the window and see that the filters are the default values for each field? ---
**Author:** ![S\_C](https://avatars.discourse-cdn.com/v4/letter/s/9dc877/32.png) [@S\_C](https://forum.inductiveautomation.com/u/S_C)\ **Post date:** [November 14, 2024, 4:59pm UTC](https://forum.inductiveautomation.com/t/preventing-conflicts-in-power-table-across-multiple-ignition-vision-clients/98618/10 "2024-11-14T16:59:49Z")
I just need to retrieve the filter's data, and its fine when I open the window the filters are default value. ---
**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:** [November 14, 2024, 5:42pm UTC](https://forum.inductiveautomation.com/t/preventing-conflicts-in-power-table-across-multiple-ignition-vision-clients/98618/11 "2024-11-14T17:42:49Z")
> [@S\_C](#): > > component's value directly to the query? Yes. ---
**Author:** ![leonardo.godoi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/leonardo.godoi/32/27178_2.png) [@leonardo.godoi](https://forum.inductiveautomation.com/u/leonardo.godoi)\ **Post date:** [November 14, 2024, 5:45pm UTC](https://forum.inductiveautomation.com/t/preventing-conflicts-in-power-table-across-multiple-ignition-vision-clients/98618/12 "2024-11-14T17:45:54Z")
Then the easiest way is like they mentioned above, to do the exact same thing you're doing with your tags but instead of tags you point each expression/value to it's corresponding parameter on your window.