https://community.databricks.com/t5/data-engineering/query-parameters-in-dashboardsqueries-can-optionally-leverage/m-p/38464#M26639 <P>Hi, I build a dashboard with dashboard parameters, it works pretty easy!</P><P>The advantage of dashboard parameters is that you do not have to set a default (it can be: all). This is convenient when you need to filter on values that change every time the query is run. However, my query-output can be long. The table has a warning that only xx rows are displayed.</P><P>It seems that values that certainly exist in the query output, show 'no data' when trying to select them in the parameter box. I suspect that only the 'displayed rows' deliver the values for the parameter. Is this correct?</P><P>I can think of two ways to avoid:</P><P>* reduce the number of selected rows. This requires prior knowledge, which I not always have</P><P>* use a query parameter instead of a dashboard parameter, but this one needs an explicit default value.</P><P>Does anyone have a hint on this one?</P> Wed, 26 Jul 2023 09:31:59 GMT Natalie_NL 2023-07-26T09:31:59Z https://community.databricks.com/t5/data-engineering/query-parameters-in-dashboardsqueries-can-optionally-leverage/m-p/4727#M1374 <P><B>Q</B><A href="https://docs.databricks.com/sql/user/dashboards/index.html?_ga=2.256674635.1762781581.1683351362-742045383.1682952714#id5" alt="https://docs.databricks.com/sql/user/dashboards/index.html?_ga=2.256674635.1762781581.1683351362-742045383.1682952714#id5" target="_blank"><B>uery parameters in dashboards</B></A></P><UL><LI>Queries can optionally leverage parameters or static values. </LI><LI>When a visualization based on a parameterized query is added to a dashboard, the visualization can either be configured to use a:</LI></UL><P>Widget parameter</P><UL><LI>Widget parameters are specific to a single visualization within a dashboard, appear within the visualization panel, and the parameter values specified apply only to the query underlying the visualization.</LI></UL><P>Dashboard parameter</P><UL><LI>Dashboard parameters can apply to multiple visualizations. When you add a visualization based on a parameterized query to a dashboard, by default the parameter will be added as a dashboard parameter. A dashboard can have multiple dashboard parameters, each of which may apply to some visualizations and not to other visualizations.</LI></UL><P>Static value</P><UL><LI>Static values are used in lieu of a parameter that responds to changes. Static values allow you to hard code a value in place of a parameter and will make the parameter “disappear” from the dashboard or widget where it previously appeared.</LI></UL><P></P><P></P><P></P><P></P> Sat, 06 May 2023 06:55:35 GMT https://community.databricks.com/t5/data-engineering/query-parameters-in-dashboardsqueries-can-optionally-leverage/m-p/4727#M1374 Priyag1 2023-05-06T06:55:35Z https://community.databricks.com/t5/data-engineering/query-parameters-in-dashboardsqueries-can-optionally-leverage/m-p/4728#M1375 <P>good info</P> Sat, 06 May 2023 07:04:46 GMT https://community.databricks.com/t5/data-engineering/query-parameters-in-dashboardsqueries-can-optionally-leverage/m-p/4728#M1375 samhita 2023-05-06T07:04:46Z https://community.databricks.com/t5/data-engineering/query-parameters-in-dashboardsqueries-can-optionally-leverage/m-p/38464#M26639 <P>Hi, I build a dashboard with dashboard parameters, it works pretty easy!</P><P>The advantage of dashboard parameters is that you do not have to set a default (it can be: all). This is convenient when you need to filter on values that change every time the query is run. However, my query-output can be long. The table has a warning that only xx rows are displayed.</P><P>It seems that values that certainly exist in the query output, show 'no data' when trying to select them in the parameter box. I suspect that only the 'displayed rows' deliver the values for the parameter. Is this correct?</P><P>I can think of two ways to avoid:</P><P>* reduce the number of selected rows. This requires prior knowledge, which I not always have</P><P>* use a query parameter instead of a dashboard parameter, but this one needs an explicit default value.</P><P>Does anyone have a hint on this one?</P> Wed, 26 Jul 2023 09:31:59 GMT https://community.databricks.com/t5/data-engineering/query-parameters-in-dashboardsqueries-can-optionally-leverage/m-p/38464#M26639 Natalie_NL 2023-07-26T09:31:59Z