Forum Discussion
Advocate IRefreshed date not updated after dataset refresh through XMLA end points
Super UserIn my reports I never rely on that "Refreshed Date" - imho it is meaningless as you can (and will) see lots of scenarios where the service is refreshing stale data over and over. Instead I use a date field from my actual data , ie "Last Modified Date" to indicate the report freshness.
- ChrisRenlund
Thanks for your input, lbendlin!
I agree from an end user perspective - In reports we normally show a Refresh date from the actual data. The issue is mainly from an administration point of view. It's quick and convenient to just go to a workspace list of datasets and get an overview of all datasets and check their latest refresh dates, ongoing refreshes and eventual failures. Using XMLA we don't see running refreshes, nor failures or updated Refreshed timestamp in that list.
Even more troublesome for us is that we use power shell scripts to refresh the data and fetch the last refreshed timestamp through an API call to compare that timestamp with indicators from our ETL-process for the data warehouse to make sure refreshes only start when all data for that dataset is available. When the Refresh date never updates our current scripts will always consider the dataset in need of a refresh.Not only is it pointless, but our end users are regularly confused by the "Data updated" display in the top panel of the app. It appears to be updated when the app has been updated. However, updating the app has nothing to do with updating the data. Do you happen to know of a way to hide this indicator in apps? Like you, I prefer to see the timeliness of the data in the report itself.
