This question was brought by my fantastisch colleague Timo Tautenhahn, who runs tableaufans.com. He was seeing some performance issues with using the Refresh commands in the JS and Extensions API, but not encountering the issues when changing a filter, which also was causing a new query to the database
In essence, whatever happens when the Refresh command fires off involves more steps than just re-querying. So the question is: what can force a re-query without the Refresh commands?
Solution: Add an Integer Tableau Parameter to a Custom SQL query that doesn’t actually affect the logic of the Query
You can have your own fun coming up with logical statements that are always true, but you don’t need anything more complex than:
SELECT * FROM table t WHERE [Tableau Parameter] = [Tableau Parameter]
As long as you change the value of the parameter to something you haven’t used yet within the session, each change should force a query refresh without using the Refresh action. Simply incrementing up from zero is enough to make it work.(more…)