Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hello Experts,
Hope you can help me.
I am now working on a power bi burndown chart that will show the plan migration of applications vs actual migration of applications.
It perfectly shows the numbers from first date to end date. However, the problem is, my date slicer is not actually showing the expected visual.
For Example:
My burndown chart shows January to December burndown.
I used calendar date (dimension table) as the x axis (date with hierarchy).
I used my fact table's date as slicer.
All items count, which burn's down until december is 120 (burndown by 10). If i use the date slicer and slice it from January to June only, it will show numbers of 60 that burn's down from january to december. Now, what we want to see is the burndown from January to June only in the visual not the whole months of the year.
Is this possible?
Thank you in advance!
Solved! Go to Solution.
Hi @v-kpoloju-msft thanks for the feedback. Been busy lately. This wasnt resolved yet. But i created a two date slicers as a mitigation in the problem. One from the Fact Table which slices the data in the visual and one from calendar table which slices the months. This i guess is good for now. But if you still have any idea where i can merge this please that would really help 🙂
Hi @uranus,
Thanks for the update and glad to hear that finding a temporary workaround using two slicers.
You're right, using one slicer to filter visuals (from the fact table) and another for month selection (from the calendar table) is a practical way to move forward when direct filtering isn't behaving as expected. To help consolidate this setup, here are a couple of approaches you could explore:
Option 1: Sync Slicers Using a Shared Date Table: If feasible, consider using only the Calendar table for both slicers and link it to the fact table via active or inactive relationships. Then, use USERELATIONSHIP in your measures to toggle context as needed. This avoids duplication and keeps logic centralized.
Example Dax query:
Sales (by Selected Month) =
CALCULATE(
[Total Sales],
USERELATIONSHIP('Calendar'[Date], 'FactTable'[YourDateColumn])
)
Option2: Use Field Parameters (if in Power BI Desktop): You can also investigate Field Parameters to allow dynamic switching between Date columns (e.g., Fact Date vs Calendar Date), which can help in merging the two slicers into one controlled experience.
If you are able to share more details about the underlying model (e.g., which dates you are comparing or filtering), I would be happy to help explore how to consolidate the slicers further.
Thank you for using the Microsoft Community Forum.
Hi @v-kpoloju-msft thanks for the feedback. Been busy lately. This wasnt resolved yet. But i created a two date slicers as a mitigation in the problem. One from the Fact Table which slices the data in the visual and one from calendar table which slices the months. This i guess is good for now. But if you still have any idea where i can merge this please that would really help 🙂
Hi @uranus,
Thanks for the update and glad to hear that finding a temporary workaround using two slicers.
You're right, using one slicer to filter visuals (from the fact table) and another for month selection (from the calendar table) is a practical way to move forward when direct filtering isn't behaving as expected. To help consolidate this setup, here are a couple of approaches you could explore:
Option 1: Sync Slicers Using a Shared Date Table: If feasible, consider using only the Calendar table for both slicers and link it to the fact table via active or inactive relationships. Then, use USERELATIONSHIP in your measures to toggle context as needed. This avoids duplication and keeps logic centralized.
Example Dax query:
Sales (by Selected Month) =
CALCULATE(
[Total Sales],
USERELATIONSHIP('Calendar'[Date], 'FactTable'[YourDateColumn])
)
Option2: Use Field Parameters (if in Power BI Desktop): You can also investigate Field Parameters to allow dynamic switching between Date columns (e.g., Fact Date vs Calendar Date), which can help in merging the two slicers into one controlled experience.
If you are able to share more details about the underlying model (e.g., which dates you are comparing or filtering), I would be happy to help explore how to consolidate the slicers further.
Thank you for using the Microsoft Community Forum.
Hi @uranus,
Just wanted to follow up one last time. If the shared guidance worked for you, that’s wonderful hopefully it also helps others looking for similar answers. If there’s anything else you'd like to explore or clarify, don’t hesitate to reach out.
Thank you.
Hi @uranus,
Thank you for reaching out to the Microsoft fabric community forum. I reproduced the scenario, and it worked on my end. I used my sample data and successfully implemented it. Used line chart.
outcome:
I am also including .pbix file for your better understanding, please have a look into it:
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.
Thank you for using Microsoft Community Forum.
thanks for being generouse and providing me the sample. Unfortunately it didnt slice the data only the visual. Or do i just need to edit relationship? My formula goes like this.
Calculate (calculate formula for the items), filter (allselected(calendar[date]), isonorafter(calendar[date],max()calendar[date]), ASC) +0
i already have the relationship where calendar filter my fact table using date.
Hi @uranus,
Apologize for the inconvenience caused. Please provide sample data that covers your issue or question completely, in a usable format (not as a screenshot). Do not include sensitive information. Do not include anything that is unrelated to the issue or question. Please show the expected outcome based on the sample data you provided.
Thank you.
Hi @uranus,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
Hi @uranus,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
Thank you.
Hi @uranus,
I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further.
Thank you.
@uranus - use the date from calendar (dimension) in your slicer.
If I answered your question please mark my post as the solution, it helps others with the same challenge find the answer!
Thanks for the feedback. I already tried this. The data was sliced. So from 120 down to 60. The burndown goes 60 to january until 0 in june. But it rose up again in july with 60 until december. It didnt slice the visual to show only 6 months.
@uranus - Then make sure it is also the date column from your calendar dimension on the visual.
Check out the July 2025 Power BI update to learn about new features.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
71 | |
70 | |
43 | |
31 | |
26 |
User | Count |
---|---|
89 | |
49 | |
44 | |
38 | |
37 |