What impact does using custom search value logic have on a component that is intended to follow a dashboard-level parameter?

• A. It ensures the dashboard-level parameter is always used
• B. It causes an error in evaluation
• C. It may cause the component to ignore the dashboard-level parameter
• D. It has no effect on the parameter usage

Answer: (C)

Custom search value logic can introduce its own source of truth for the value the component uses. When a component is meant to follow a dashboard-level parameter, it expects to pull that value from the dashboard’s parameter binding. If you add custom logic to determine the search value, the component may compute a value that differs from or bypasses the dashboard parameter. In that case, the component ends up ignoring the dashboard-level parameter because its filtering is driven by the custom logic instead of the centralized parameter. This isn't necessarily an error; it's just the component prioritizing its own calculation over the shared parameter, which can lead to inconsistent filtering across the dashboard. To avoid this, align the custom logic with the dashboard parameter or ensure the component binds to the parameter and respects its value.