Forum Discussion
SSAS Connector dashboard refresh issue
The one behavior that I noticed, possibly has impact on dashboard tiles refresh.
- The PowerBI is running DMV query to check the schema (and expects more recent date timestamp?)
select [date_modified] from $system.dbschema_catalogs where [catalog_name]='Model database name')
- This date gets updated only when the tabular model is processed from SSMS (ProcessFull or ProcessRecalc). It is not updated when the processing is launched from SSIS package in XLMA mode through script task or XMLA is run from query window.
- PowerBI then terminates the connection instead of running DMX queries to refresh.
- When I process the model from SSMS manually, then the next check, runs the DMX queries and refreshes the tiles.
- PowerBI checks do not come in every 15 mins for sure. (Came in at 11.08 AM and then 2.13 PM for example)
- Have not figured out a way to force the date_modified which corresponds to Last Schema update from script. Only the Last processed date/time gets updated.
Hope this gets fixed as we are exclusively using SSAS On-prem as data source.
I have got the exactly the same problem! I can see in the profiler the service polling SSAS using
select [date_modified] from $system.dbschema_catalogs where [catalog_name]='catalog_name'
but the tiles aren't refreshing at all. Fingers crossed this is fixed for GA on Friday.
- jonno23211 years agoRegular Visitor
I didnt think to check this. Mine seems to be working better now.
- dm-p11 years agoSuper User
I'm still having this issue since GA... for DirectQuery mode - drilling into reports shows "live" data. I'd tested with In-Memory but opted to switch out to DirectQuery so we can keep an eye on things within a window of 10 mins or so without having to constantly process our model (we found ~2 hours acceptable for most of our data but there are a couple of metrics we'd like to know about sooner).
This works just fine in the report view but the dashboard remains static unless I re-deploy the model to our SSAS instance (as it's DirectQuery, re-processing does not do anything) or navigate to the report and re-pin the items to the dashbopard, which is kind of onerous!
My other option would be to push these events via the API but as it's not a particularly huge dataset I felt that DirectQuery would probably give us a happy medium. I think for now I'll see if our folks are happy with moving back to In-Memory with a shorter processing interval.