Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
Good day,
I am trying to build a kpi scorecard for multiple dept
i was tasked to have 2 slicers
slicer1 = buttons FYYTD, YTD,, QTR, Month, woy, Day
slicer2 = date picker
1. slicer1 only controls the grain of slicer2 and based on selection, filter(fytd, ytd), grain(qtr/month/woy/day)
- 1.b. would I requre a custom field?
2. Can a date picker grain be altered, based on the grain selection, would a date picker slicer be the best option - alternatives?
Please help?
Solved! Go to Solution.
Hi @icassiem ,
Based on your description, you want to create an interactive report where one slice controls the granularity of the date selection in another slice.
For your first question, it is not necessary to have custom fields to do one slice control dates in another slice. You can use the slicer's built-in functionality to control the granularity. For example, if `slicer1` is set to `Month`, you can restrict `slicer2` (the date picker) to show only months. You can use the Edit Interactions feature in Power BI to specify how slices interact with each other and other visualizations.
Second question: While you can't directly change the granularity of a date picker slice based on a selection in another slicer, you can create a series of date pickers, each with a different granularity, and then use the Edit Interactions feature to control which picker is active based on the selection in `slicer1`. As for other alternatives, you might consider using a relative date slicer or a numeric range slicer, which can provide similar functionality but with a different user experience.
For more information on the use of slicers you can refer to this document
Slicers in Power BI - Power BI | Microsoft Learn
Best regards,
Albert He
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly
Hi @icassiem ,
Based on your description, you want to create an interactive report where one slice controls the granularity of the date selection in another slice.
For your first question, it is not necessary to have custom fields to do one slice control dates in another slice. You can use the slicer's built-in functionality to control the granularity. For example, if `slicer1` is set to `Month`, you can restrict `slicer2` (the date picker) to show only months. You can use the Edit Interactions feature in Power BI to specify how slices interact with each other and other visualizations.
Second question: While you can't directly change the granularity of a date picker slice based on a selection in another slicer, you can create a series of date pickers, each with a different granularity, and then use the Edit Interactions feature to control which picker is active based on the selection in `slicer1`. As for other alternatives, you might consider using a relative date slicer or a numeric range slicer, which can provide similar functionality but with a different user experience.
For more information on the use of slicers you can refer to this document
Slicers in Power BI - Power BI | Microsoft Learn
Best regards,
Albert He
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly
Thank You very much @v-heq-msft
I missed that based on slicer1 selection the slicer2 picker must default to YTD, MTD, Year, day(curr), week(curr) selections - how can i achieve this as the date picker doesnt not change selection?
do i need a button or something after the sclicer2 date defaults to action the visuals?
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
38 | |
27 | |
17 | |
16 | |
8 |
User | Count |
---|---|
46 | |
38 | |
34 | |
16 | |
16 |