Forum Discussion
Cannot create a Time Intelligence Measure in the Warehouse
- Anonymous2 years ago
Hi Luci7 ,
We have an update from internal team.
If the two datasets have a different structure, its okay for the syntax to be different.
In Power BI Desktop, a valid measure expression could read:
DAXCopy
Date Count = COUNT(Sales[OrderDate].[Date])Note:
While this measure expression is valid in Power BI Desktop, it's not correct DAX syntax. Internally, Power BI Desktop transposes your expression to reference the true (hidden) auto date/time table column.
Hope this is helpful.
Hi Anonymous
I doubled checked and you're right, if we use:
DATEADD('table'[column], -1, MONTH)
It works in Fabric, but if you go to Power BI Deskto the correct syntax is
DATEADD('table'[column].[Date], -1, MONTH)
Do you know if Microsoft is changing the Time Intelligence DAX syntax in Fabric?
Hi Luci7 ,
Thanks for using Fabric Community and reporting this .
I have reached for the internal team for help on this. I will update you once I hear from them.
Appreciate your patience.
- Anonymous2 years agoNot applicable
Hi Luci7 ,
We have an update from internal team.
If the two datasets have a different structure, its okay for the syntax to be different.
In Power BI Desktop, a valid measure expression could read:
DAXCopy
Date Count = COUNT(Sales[OrderDate].[Date])Note:
While this measure expression is valid in Power BI Desktop, it's not correct DAX syntax. Internally, Power BI Desktop transposes your expression to reference the true (hidden) auto date/time table column.
Hope this is helpful.- Luci72 years agoHelper I
Hi Anonymous ,
I see!! This is why! In Power BI Desktop we have the "auto date/time table" but not in Fabric, hence, the date column is not automatically converted to show date hierarchy.
Thank you for the clarification!! That helps a lot.Have a nice day!
Kind regards.
- Anonymous2 years agoNot applicable
Hi Luci7 ,
Glad to know your issue got resolved.
Please continue using Fabric Community for help regarding your issues.