In an advanced dashboard with SlicerDicer and metric components, a parameter change updates SlicerDicer but lags for metrics. To synchronize in real-time for complex queries, what?
A.
Set both to use the same summary level parameter and enable propagation in IDN definitions
When a parameter change updates a SlicerDicer component promptly but the metric components lag, the remedy is to make both component types respond to the same summary level parameter and to enable propagation in the IDN definitions. Metric components read their values through the metric definitions stored in IDN, and these must be told which dashboard parameter they should honor. If the metric definition is not linked to the parameter, the component continues to display values for the previous selection until its own refresh occurs. The first option is correct. Using separate parameters would force users to change two selections and would invite inconsistent views. A manual refresh button treats the symptom and leaves the design unsynchronized. Moving every component to SlicerDicer would change the content and is not always possible, because metrics offer features such as targets and benchmarking that sessions do not. After the configuration is changed, the developer should test the dashboard with several parameter values and with different user roles, and confirm that both component types change together.
[Reference: Cogito Fundamentals – Radar Dashboards and Components: Synchronizing Parameters Across Component Types, ===============, ]
Contribute your Thoughts:
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