Bora Beran at some point someone inside Tableau is going to do a Refresh data flow chart, right? Something like the order of execution diagram, I hope. We get these questions all the time on the forums; and have no idea who (or what KB article) to send them to.
I personally would love to see a Tableau 'refresh' diagram!
Let me see if we can put together some sort of a KB article for this
Can anyone please let me know if there is a solution for this issue? I'm experiencing the same behaviour:
Most of our dashboards are based on extracts. Those extracts are refreshed every night using Tabcmd, which is working great. When I open the workbooks in my browser in the morning, they are correctly showing the new data. However, if I refresh the extract again (with new data in the underlying source), the dashboard/view will still show old data. When I hit "Refresh", it indeed shows the new data, but if I re-open the view, the old data will be shown again.
It shouldn't be related to my browser's cache, as using a different browser will still show the old data.
Looking at other threads about this topic, it seems that even with the "Refresh less often" Cache setting in Tableau Server, the cache should be cleared in case of a refreshed extract. To me, this doesn't seem to be the case. Am I missing something?
Your help will be appreciated, thanks a lot!
Thanks for your quick reply!
However, I'm expecting that pressing the "Refresh" button will really clear the cache, instead of just ignoring it. See also Refresh Data or Pause Automatic Updates , which also mentions clearing the cache.
If the cache would be cleared, it doesn't explain why I still see the old data if I re-open the workbook.
Also, according to some information, I'm expecting the cache to be cleared as soon as an extract has been refreshed. See Russell's reply at Re: How often is "Refresh Less Often" .
I agree it sounds weird. Not sure why it happens.
Glad to hear I'm not the only one. I'm experiencing this same issue and we are on the most recent version: 2018.2.0. Having to hit the Refresh Button to get the most up to date data is ridiculous to me. A user shouldn't have to hit the refresh button; it's not only a poor user experience but it makes the developer of the dashboard look bad! Try explaining to a business user, especially an executive, why they need to hit that button....
According to this article https://kb.tableau.com/articles/issue/view-out-of-date ,
"Each process has its own cache stored in RAM, which is why clicking Refresh Data does not refresh data for every user. Different user sessions are handled by different VizQL processes, and Refresh Data only removes the cache of the current process." .
Does someone know a way to trigger a cache refresh after a datasource extract for a workbook that will apply to all views and all users/processes?
Could this be done by using the :refresh=yes option in one of the workbook views or it would just refresh the data for that user?
Thanks Dimitris, I think that KB article explains the behaviour and why old data seems to come back when a user has hit refresh on a previous browser session. My treatment has been to embed refresh=y in bookmarks for those users who need it. it's a rare complaint so wasn't too much in trouble in my business.