Forum Discussion
Time Intelligence with Direct Query
Best
Darek
HI,
so what I did:
- created an Azure Data Warehouse with AdventureWorks DW sample DB
- deleted 2006 data from dimDate because there's a gap in the date table, Power BI isn't happy with that. There's no sales data for 2006...
- created a DirectQuery model with Power BI latest version
- selected DimDate and FactInternetSales
- built up a relationship between FactInternetSales.OrderDateKey and DimDate.DateKey
- I marked DimDate as Date Table with FullDateAlternateKey as the date field
- Tried to create a Quick Measure with Time Intelligence but the corresponding section isn't available in the calculation list
What works is DAX formulas like DATESYTD() but this is independent of using a separate date table or not. So still I'm confused what extra functionality should be enabled with a date table in the DirectQuery source compared to anything else...
THANKS
Thomas
- Anonymous7 years agoNot applicableTime-intel functions ALWAYS rely on a separate Date table that stores contiguous dates for whole years. This is how it works. If you use them on something that is not a Date table, you'll get rubbish.
Best
Darek - Anonymous7 years agoNot applicableMy guess is that quick measures just don't work (yet?) with DirectQuery.
When in doubt, go to documentation:
https://docs.microsoft.com/en-us/power-bi/desktop-quick-measures#limitations-and-considerations
And now you know...
Best
Darek- TePe7 years agoHelper IV
yep, might be the case that DirectQuery isn't supporting TimeIntelligence Quick Measures... The DAX formulas seam to work so it's just additional effort to build the measure manually...
Thanks,
Thomas
- Anonymous7 years agoNot applicableThe link I showed you in my previous post says clearly that quick measures do not work in DirectQuery. It's not "might be", it's 100%.
Best
Darek