Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
I defined some DAX measures in Excel 2013 based on a facttable with dates linked to a date table.
All measures correctly show their value by month (from the date-table) in a Powerpivot. I import the model into Power BI Desktop (March update). When I use a table or a line chart visual to plot them, the two measures that directly rely on the data in the fact table correctly plot the values by months. Other measures (doing some sort of calculations, e.g. % fill rate by months vs. final value in year) only show values for a single month or nothing at all.
Are date-based measures handled differently in Powerpivots and Power BI? Is there a way to change that behavior?
BTW: the same issue occurs when I plot the measures in a Poverview line chart - some measures are not (fully) displayed.
Solved! Go to Solution.
I found the issue: the date table in Excel was corrupt. I could only select the columns in the fact table as unique identifiers for the date column (?)
Rebuilding the date table from scratch solved the problem.
How are your tables joined? To my knowledge, the only difference is that you must use a date column to join the tables in Power Bi. In Excel you can also join the tables with surrogate keys - eg 20160101 as a date column. Is this your use case?
I model the join with a date column already in Excel and just import to Power BI Desktop. Just checked there: still using that column with data/time format.
Interesting for me is to see that behavior already on the Excel side: Powerview does not plot the measures either. Only the Powerpivot table shows it correctly.
Well I guess it is either a bug, or it isn't. The challenge is to find out which. I would be happy to take a look if you can share with me. You can contact me via my website http://xbi.com.au or you could log a bug with MS
I found the issue: the date table in Excel was corrupt. I could only select the columns in the fact table as unique identifiers for the date column (?)
Rebuilding the date table from scratch solved the problem.
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the October 2025 Power BI update to learn about new features.