Radar components are configured in the Component Editor, where two settings decide what a component can display: the display format and the data source. To place a SlicerDicer session on a dashboard, the component must use SlicerDicer as its data source, since that setting tells Radar where to retrieve the data. The display format must be a graph, because the visualization that SlicerDicer exposes to a component is its chart output, which makes Graph with SlicerDicer the required pairing. A table display is not offered for this data source, and the options pairing a Report data source with either a table or a graph describe components based on Reporting Workbench reports, not on SlicerDicer sessions. The practical workflow is to build and save the session in SlicerDicer, create a new graph component, select the session as its source, and then add the component to a dashboard through the Content form of the Dashboard Editor. Because the component refers to the session, changes to the session will flow through to the dashboard. This is why the session must be saved first.
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