Slices break the population into subgroups according to a characteristic such as provider, age or department, and the measure is then calculated for each subgroup. They provide the comparison that a single total cannot, so that a user can see where the highest and lowest values occur. The third option expresses this accurately. Small reports embedded into dashboards describe components in Radar and are not slices. Bar colors in graphs are a formatting feature with no relation to how data is grouped. Filters used to access the Component Editor are not a SlicerDicer concept, as the Component Editor is a separate developer tool. A slice does not exclude anyone from the population; it only organizes the people already in it, which is the difference between slicing and applying a criterion. The user can apply more than one slice to look at the data in finer detail, and may drill into a particular subgroup to see its members. When a session shows a single bar and the requirement is a comparison across categories, adding a slice is the appropriate action, and the choice of field should reflect the grouping that decision makers are interested in.
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit