Forum Discussion
Slicer selection for bins
Hiya.
At this very moment it's not entirely clear to me what you want. Would you please enlarge a bit upon it? Some pics would certainly help. I need to see your model and some rough visualization(s) of what it is you need.
Thanks.
Best
Darek
Anonymous ,This is the snapshot of the visualisation. This contains time being converted to bins with bucket size of 1 hour which you can see. I want the report user to change the bin bucket size to see the values.
Hope Its clear now and expecting valuable help.
- Anonymous7 years agoNot applicable
Hi there.
Mate, please contemplate this:
The x-axis changes accordingly to which time bucket you select:
This is what you wanted, right?
Here's a file that shows you how to achieve it.
Best
Darek
- vissvess7 years ago
Helper V
Dear Anonymous ,
Thanks for getting back with a valuable solution. Happy to hear from you.
The solution is great but my data set is different. I am not able to unpivot my data with as many with 5 new columns representing bucket sizes as the data is huge.
Lemme elaborate.
The snapshot I shared was created using New group--> bins. See below.
Here the bin size entry is not dynamic. I was looing around a way to make it dynamic based on selection.
But the above steps gives me a calculated column (Time(Bins)) in my modelling tab as follows.
Based on above 3 Hour selection, a column based on time column is created stating which bucket it falls on.
I thought of automating that in another way based slicer selection.
--> So, I have created a isolated table with single column containing 1hr/2hr/3hr/4hr/8hr.
--> A slicer for the column
-->Then I am now looking for an expression which if one of the 1hr/2hr/3hr/4hr/8hr is selected, based on the value the calculated column to be calculated.
Does this way help be solve the scenario.? Could anyone help with the expression.?
Thanks
- Anonymous7 years agoNot applicable
Mate, use PQ to prepare your data, not DAX. DAX is not a tool for that.
Secondly, if you want to have dynamic x-axis, you don't have a choice. Thirdly, good fact tables in PBI should be narrow and long, with columns where there are not many distinct values. Such tables compress extremely very well, even up to 100x. I'm not sure why you'd be so concerned about size... Besides, you could completely transform your fact table and have 2 tables side by side.
You need to be FLEXIBLE. Think outside the box.
Best
Darek