A metric-based component on a Radar dashboard displays inconsistent data across user groups. The component uses Dashboard Resources with summary targets. What could be causing this issue?
A.
User groups have different Reporting Workbench security classes.
B.
The component ' s Summary Target Lookup Method is set to " Group-Specific. "
C.
The SlicerDicer session is not updated in Caboodle.
D.
The dashboard ' s Access form excludes certain user groups.
Metric components that rely on summary targets can show different results for different users or groups when the lookup method is tailored to context. The correct explanation is: the component ' s Summary Target Lookup Method is set to " Group-Specific. " . With a user-, group-, department- or region-specific method, each person is compared against a target appropriate to them, so two viewers can see different comparisons for the same component. If the organization wants a single common target, the method should be changed to a global or standard option. The alternatives mention security classes, session updates or access forms, which would cause missing content or access problems and not different target values. The developer should decide with the business owner whether tailored targets are intended. If they are, the component should say so; if not, the lookup method should be corrected and the thresholds checked. Where several settings could plausibly be responsible, changing one at a time and retesting after each change makes it possible to learn which setting actually solved the problem, which is useful knowledge for later maintenance.
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