View 1 contains a table bound to a tag with a named query. User selects a record, clicks edit, opens a popup to view/edit the details. User selects the new value to replace the old value, clicks confirm changes, and another tag with a named update query runs.
How do I get the View 1 table data refreshed? It still displays the old values, even with a browser refresh.
Why would you do that with a tag? Updates are generally done in an action script. The table probably should have the named query directly bound, and then your action script can request a refresh after the update operation completes.
Don't use gateway tags for UI elements, unless you expect the value to be broadcast to all possible clients.
No, only tags created in the Vision Client Tag provider. Such tags are per-client at runtime, and are commonly used to hold client-wide (but not system-wide) state.
System-wide state is held in gateway tags (the default and other real-time providers). UI data should not go through gateway tags unless it is so commonly displayed on all/most clients that broadcasting efficiently via tag makes sense.
Yes, unless the binding is set to polling. But that burns CPU on gateway and DB to no purpose in most cases. Use .refreshBinding() when you know the data has changed (because you just changed it, typically).