Forum Discussion
Grouping Values
Hi Kolumam,
Try the following steps
1. Import your data set
2. Create 2 more references of your data set
3. Now you will have 3 copies of your data.
4. Filter the data sets as follows
Filter your 1st data set such that you have data for those records where the number column will have values between 1 and 10,
2nd data set will have data for those records where the number column will have values between 1 and 15,
3rd data set will have data for those records where the number column will have values between 1 and 20,
5. Now create a static column.
In the 1st data set, this column should have 1-10 as the data
In the 2nd data set, this column should have 1-15 as the data
In the 3rd data set, this column should have 1-20 as the data
6. Now append (union) these 3 queries
7. After appending, you will have a single dataset will 3 sets of similar data
8. Now use distinct values of this new column in your slicer selection.
9. Your visual should have data from this new data set
10. Changing Selections in the slicer will not filter the data for the groups
But this has couple of limitations.
1. Atleast one group in the slicer should always be selected. If not selected, the all the 3 copies will be displayed, which is not right
2. This will result in multiple copies of the same data. But this will not affect performance as we are using reference
In case of queries, let me know. Will try to help
Hope this solves your requirement!!!
Hi Anonymous, Zubair_Muhammad
The issue is if I make group B for years 1 to 15 as 1-15 and leave out the rows 16 to 20 as blank...when I add the slicer it is showing another option as blank
Eg. Group B
1-15
Others
How do I fix this issue?
If you are creating a report around group B, create a page based filter that excludes everything except Group B 1 - 15.
If you are trying to create a report with Group A and Group B on the same report, you are mixing contexts and they will conflict.
Is there any solution to display both 1-10 and 1-15 as slicers without any conflicts?
The slicers show the line items in the table for the page context. So if a page wants to exclude a row for a certain slicer then it will be excluded for the other slicer too. The solution you need is simply what you previously suggested. The unwanted categories should be listed as "Other" or some moniker to suggest they shouldn't be selected, but not actively preventing someone from doing so.
This will mean your slicers will act like "I want rows that conform with my Group A selection and also conform to my Group B selection" (if you make a selection from both). If only a single slicer is selected, then you get the rows associated with that single selection.