Supplies are limited. Contact info@espc.tech right away to save your spot before the conference sells out.
Get your discountScore big with last-minute savings on the final tickets to FabCon Vienna. Secure your discount
Hi All,
I have been using both import and direct query in my desktop using a composite model that was released in this month. However, when I try to create a relationship between them, the cardinality is many to many by default and it cannot be changed. When I tried to filter them, it doesn't work. So I tried converting from direct query to dual and I was able to filter it correctly using many to many. Now, I have the following questions:
1) How does dual storage works and is it same as the direct query?
2) If I configure schedule refresh for a dataset that has both dual and import, does it refreshes according to the scheduled refresh or they refresh individually? (Meaning to say if dual depends on schedule refresh or not)
Please help.
Thanks
Hi @Kolumam,
1) How does dual storage works and is it same as the direct query?
Dual tables have the same constraints as DirectQuery tables. These constraints include limited M transformations and restricted DAX functions in calculated columns. For more information, see Implications of using DirectQuery.
2) Based on my test, it refreshes according to the scheduled refresh.
Regards,
Frank
If Dual storage uses schedule refresh, then I can use import for that. I am not asking for constraints, does it pull the data live?
Why the hell is this feature then used for?
Hi @Kolumam,
Dual tables can act as either cached or not cached, depending on the context of the query that's submitted to the Power BI dataset. In some cases, you fulfill queries from cached data. In other cases, you fulfill queries by executing an on-demand query to the data source.
For more details, please check the online document.
Regards,
Frank
Hi @Kolumam,
Does that make sense? If so, kindly mark my answer as a solution to close the case.
Regards,
Frank
Not the answer that I was looking for.
Please read my question properly.