Dual Storage Mode - not acting as direct query

[dmac412]

Hi everyone, 

So I have a few questions about a dual storage mode table. 

I have an aggregate ( composite) model setup with a few dimensions in dual storage mode.

We embedded our report and on the website give the user ability to change some aspects of a dimensions (group things together ect.). They expect to see the changes instantly. Since the dual table stores a version of the table in memory, we dont see the changes take effect instantly. When refreshing the model they will come through. 

Is this performing as designed?Is there a way to get the table to act as direct query? Through the api can i force a refresh of one table? xmla endpoint may be able to refresh one table but i dont think its out yet?

[d_gosbell · Accepted solution]

---

Is this performing as designed?

---

Yes this is performing as designed. When you have aggregations it's up to you to manage the refreshing of the import and dual mode tables.

Is there a way to get the table to act as direct query? 

---

I think you'd have to switch the table out of dual mode and make it Direct Query. But then any query using this table would not be able to use the aggregations.

Through the api can i force a refresh of one table? xmla endpoint may be able to refresh one table but i dont think its out yet?

---

I think the xmla endpoint is the only way to do this. This feature is still in preview, but If you have the model on premium capacity you should be able to enable the xmla endpoint on your workspace.