We've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
Hi everybody,
I'm preparing a report with a double dynamic segmentation that doesn't work, so I ask your help.
I've got a table with dates, locations and number de events, similar to:
| Date | Location | Number of events |
| 01/09/2020 | Madrid | 10 |
| 01/09/2020 | Barcelona | 1 |
| 01/09/2020 | Sevilla | 2 |
| 02/09/2020 | Madrid | 2 |
| 02/09/2020 | Sevilla | 8 |
| 03/09/2020 | Barcelona | 1 |
| 04/09/2020 | Madrid | 1 |
And in the report I have 2 data segmentations, () one for "dates" and the other for sum of "number of events". The limits of this one (sum of "number of events") must be between the allowed possibilities according to the date segmentation.
With the one for "dates", obviously, I filter the dates, and with the one for "number of events", I want to retrieve the locations whose sum of events in the filtered period are between the marked limits and the sum of their events.
Examples:
A) if I select in date segmentation:
Then, the sum of "number of events" segmentation must be:
If, in this case, I don't move the "number of events" segmentation, the result must be:
But, if I select:
I must get the locations whose sum of events in this period are between 7 and 13:
B) If the date segmentation is:
Then, the sum of "number of events" segmentation must be (please, notice that now it's between 2 and 8, due to the number of events it's something dynamic in the original data):
So, in this case, the result must be:
And, if I move the maximum from the sum of "number of events":
The result must be:
Can someone help me to solve this issue?
Thanks in advance.
Best regards!
Solved! Go to Solution.
HI @EmilioMadrid,
So you mean the second slicer should be dynamic changes based on the selection of slier1?
If this is the case, it not an issue, both slicers are work as expected. You can use the slicer to filter another slicer items(power bi use and logic to link filters) but selected filter range not able to dynamic changes based on the filter interactions.
Regards,
Xiaoxin Sheng
HI @EmilioMadrid,
So you mean the second slicer should be dynamic changes based on the selection of slier1?
If this is the case, it not an issue, both slicers are work as expected. You can use the slicer to filter another slicer items(power bi use and logic to link filters) but selected filter range not able to dynamic changes based on the filter interactions.
Regards,
Xiaoxin Sheng
Hi, Xiaoxin,
Thanks for response. So, sadly, it's something that can't be done.
Regards.
@EmilioMadrid , the date should work with slicer. For the Number of events you need segmentation
example: https://youtu.be/czNHt7UXIe8
or
https://www.daxpatterns.com/dynamic-segmentation/
https://www.daxpatterns.com/static-segmentation/
https://www.poweredsolutions.co/2020/01/11/dax-vs-power-query-static-segmentation-in-power-bi-dax-po...
https://radacad.com/grouping-and-binning-step-towards-better-data-visualization
Hi, Amitchandak, thanks a lot.
I'm not so professional as you to solve this problem. The first part, the date slicer is easy and I had done it before.
The problem to me is to get the second slider, that must be dynamic, in the sense that the first value that let you to select and the last one must be the extremes of the possible values in the previously selected date range.
I've read the links that you attached, but, as I mentioned, I'm not so good in PowerBI yet and the tests that I have done based on them have failed...
If you could give me a small solution based on my example I would appreciate it infinite.
Thanks a lot.
Emilio.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 57 | |
| 38 | |
| 33 | |
| 19 | |
| 16 |
| User | Count |
|---|---|
| 68 | |
| 66 | |
| 41 | |
| 34 | |
| 24 |