In the scenario where two reports from the same template have one graph component that does not respect the dashboard level parameter, which reason is most likely?

In the scenario where two reports from the same template have one graph component that does not respect the dashboard level parameter, which reason is most likely?

• A. The parameter does not allow overrides
• B. The parameter is in a related group
• C. The parameter uses custom search value logic
• D. The parameter is not visible

Answer: (C)

The key idea is that a component can control its own data selection independently from the dashboard-wide parameter. When two reports from the same template differ only in one graph not respecting the dashboard level parameter, it points to that graph using its own internal rules for determining values—specifically, custom search value logic. This means the graph builds its query or filters in a unique way, rather than simply inheriting or applying the dashboard parameter value. As a result, the graph can pull different data or interpret the parameter differently across reports, even though the rest of the template and dashboard parameters align. The other possibilities don’t fit this symptom as directly. If a parameter didn’t allow overrides, it would affect whether values could be changed rather than explain a single component diverging from the dashboard parameter. If a parameter is in a related group, it would influence dependencies, not cause one graph to ignore the dashboard parameter. If a parameter isn’t visible, you wouldn’t see or be able to set it, but that wouldn’t explain a graph that still appears and uses a different internal logic.

The key idea is that a component can control its own data selection independently from the dashboard-wide parameter. When two reports from the same template differ only in one graph not respecting the dashboard level parameter, it points to that graph using its own internal rules for determining values—specifically, custom search value logic. This means the graph builds its query or filters in a unique way, rather than simply inheriting or applying the dashboard parameter value. As a result, the graph can pull different data or interpret the parameter differently across reports, even though the rest of the template and dashboard parameters align.

The other possibilities don’t fit this symptom as directly. If a parameter didn’t allow overrides, it would affect whether values could be changed rather than explain a single component diverging from the dashboard parameter. If a parameter is in a related group, it would influence dependencies, not cause one graph to ignore the dashboard parameter. If a parameter isn’t visible, you wouldn’t see or be able to set it, but that wouldn’t explain a graph that still appears and uses a different internal logic.