Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredJoin us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered
Hey everyone,
Good day! I've run into a weird scenario. In Power BI Desktop, I was able to create quick measures, especially the time intelligence ones. But the moment I throw the DAX into the Warehouse, it didn't work. The ".[Date]" part of the code is not working. I've got this column that's tagged as 'date' in my dataset, but it's like the Warehouse is playing blind. Anyone else tried making time intelligence measures in the Warehouse? A little guidance would be gold right now. 🤔
Below is an example of the DAY I copied and paste from Power BI Desktop to MS Fabric Warehouse:
Solved! Go to Solution.
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 @Luci7 ,
Following up to see if the below comment was helpful. And, if you have any further query do let us know.
Hi @Luci7 ,
Following up to see if the comment was helpful. And, if you have any further query do let us know.
Hi @Luci7 - Welcome to Fabric Community platform and thanks for posting your question here.
As I understand you are trying to execute a query with DATEADD() function in DAX . It seems like there is some syntactical error in the query. Please check the below points regarding DATEADD function in DAX:
1. The first column of the DATEADD function should have the type date and return a single-column data table.
2. When you add or subtract any interval from the date, you will get only those dates available in your date table.
3. After shifting the date interval forward or backward, the DATEADD function will only contain those shifted dates that are available in the data table; otherwise, it will return blanks
Sample Query: DATEADD(DimDate[Date],-1,MONTH)
For more details , kindly check this document: https://www.learndax.com/dateadd-dax-function-and-related-issues/
Since your query is more inclined towards PowerBI directly, I would recommend you to post your issue directly on PowerBI official community forum: Microsoft Power BI Community - Microsoft Fabric Community
Hi @Anonymous ,
Thank you for the welcome and for your reply!
I thought would be useful to put my question here because the error I am only getting an error using this formula in Fabric, not Power BI Desktop. In Power BI Desktop I am using this formula successfully and it can be found in the "quick measure" part.
There, in Power BI Desktop I don't get any error, but in Fabric, using the same formula, I got an error and Fabric doesn't recognize my date column as a date type, because it gives me an error when I try to use formulas related to date, like for example, DATEADD.
Could you please inform if you use, in Fabric, any function related to time in a date colum type? It worked?
Thank you for your help!
Kind regards
Hi @Luci7 ,
I am able to use DAX DATEADD() in my Fabric Warehouse without any error.
Can you please cross verify your syntax and also try to share few screenshots in order to identify exact issue.
Working with DAX DATEADD():
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.
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 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.
Hi @Luci7 ,
Glad to know your issue got resolved.
Please continue using Fabric Community for help regarding your issues.
User | Count |
---|---|
2 | |
1 | |
1 | |
1 | |
1 |
User | Count |
---|---|
5 | |
3 | |
3 | |
2 | |
2 |