Forum Discussion
Calculated table does not refresh after published to Workspace
Hi ImNewUser ,
Based on my test, for calculated table in direct query, that is kind of import. So in your scenario, you should set schedule refresh of your dataset to make it keeping refreshed. As the picture below, we can only set schedule refresh not cache refresh.
Hi v-frfei-msft ,
No I did not perform any scheduled dataset refresh, because the underlying table is a direct query.
From the above, "VillageTable" is the calculated table and "V_TAR_OutageVillageBase" is the query that the calculated table pull data from.
However, it seems that even if I explicitly click "Refresh", the table of directquery refreshed, but the calculated table does NOT refresh.
Please help...
Hi ! I too am experiencing this issue and would like to know how to overcome. Crafting reports with direct query is meant to keep the report always current such that a user doesn't have to worry about refreshes or schedule cycles (which, due to limits on the number of cycles per day, does not enable one to keep a report always current). One would think that hitting refresh should trigger calculated tables to refresh to align to the underlying data, and if the underlying data is direct-query driven, the calculated table should always be in sync. What's the way forward ? If I have to schedule a refresh simply to update calculated tables based on direct query data, that's a severe limitation to the advantage of direct queries (ie "only use direct queries if you have no calculate tables").