diff --git a/_docs/master/dashboards/filters.md b/_docs/master/dashboards/filters.md index 6407c4c95d..230db2f4e2 100644 --- a/_docs/master/dashboards/filters.md +++ b/_docs/master/dashboards/filters.md @@ -16,20 +16,24 @@ redirect_from:  -Have you ever found yourself in a situation where it seems like you need to create nearly identical copies of the same dashboard, with just one different variable? Maybe you have an Earnings dashboard, but you want to see the data for each city your business is in, or maybe you have a KPI dashboard that you want to see broken out by month. +Instead of creating duplicate dashboards to show different cuts of the same data, you can add filter or parameter widgets to let people change variables for cards on a dashboard. -Instead of creating duplicate dashboards, you can add filter or parameter widgets to let people change variables for cards on a dashboard. - -## Adding a filter or parameter +## Adding a filter or parameter widget to a dashboard, heading, or card  -- Click the **pencil icon** to enter dashboard editing mode. -- Click the **filter icon** that appears in the top-right to add a filter. -- Select a [filter type](#filter-and-parameter-types) -- [Connect your filter or parameter widget to dashboard cards](#connecting-a-filter-or-parameter-widget-to-dashboard-cards) to one or more dashboard cards on any or all tabs. -- [Configure your filter](#editing-a-filter) -- **Save** your changes. +1. Click the **pencil icon** to enter dashboard editing mode. +2. You can add a filter or parameter widget to: + + - **The whole dashboard**. Metabase will only display dashboard-level widgets if they're connected to a card on the current tab. + - **Heading cards**. Not text cards, only [heading cards](./introduction#adding-headings-or-descriptions-with-text-cards). Can only be connected to cards on the current tab. + - **Question cards**. Can only be connected to cards on the current tab. + + Go to where you want to add a filter and click the **filter icon**. +3. Select a [filter type](#filter-and-parameter-types). +4. [Connect your filter or parameter widget to dashboard cards](#connecting-a-filter-or-parameter-widget-to-dashboard-cards) to one or more dashboard cards. Only dashboard-level widgets can be connected to cards on multiple tabs. +5. [Configure your filter](#editing-a-filter) +6. **Save** your changes. Metabase will display the filter only if the filter is connected to a card on the current dashboard tab. @@ -39,7 +43,7 @@ The type of filter or parameter widget you choose determines how the widget work ### Filter widgets -**Filters** determine what data to show. For example, a date filter might show only data from the last 30 days, or a category filter might show only specific product categories. +**Filters** determine _what_ data to show. For example, a date filter might show only data from the last 30 days, or a category filter might show only specific product categories. - [Date picker](#date-picker-filters) - [Location](#location-filters) @@ -50,13 +54,13 @@ The type of filter or parameter widget you choose determines how the widget work ### Parameter widgets - **Parameters** determine how to show the data. The time grouping parameter, for example, changes the granularity of time-based visualizations (like showing data by month instead of by day) without removing any data points. + **Parameters** determine _how_ to show the data. The time grouping parameter, for example, changes the granularity of time-based visualizations (like showing data by month instead of by day) without removing any data points. - [Time grouping](#time-grouping-parameter) ## Date picker filters -When picking a Time filter, Metabase will prompt you to pick a specific type of date picker widget: +When picking a Date picker filter, Metabase will prompt you to pick an operator: - Month and Year - Quarter and Year @@ -65,19 +69,17 @@ When picking a Time filter, Metabase will prompt you to pick a specific type of - Relative Date - All Options -Single Date and Date Range will provide a calendar widget, while the other options all provide slightly different dropdown interfaces for picking values. To get a widget that's just like the time filter in the query builder, choose All options. +Single Date and Date Range will provide a calendar widget, while the other options all provide slightly different dropdown interfaces for picking values. To get a widget that's just like the date picker in the query builder, choose All options. ## Time grouping parameter  -You can add a time grouping widget to a dashboard to change how charts are grouped by time. For example, you may want to look at the time series charts grouped by month by default, but give people the option to view the results by other groupings: by week, by quarter, and so on. - -> Time grouping parameter widget can only be connected to questions built with the [graphical query builder](../questions/query-builder/editor). +You can add a time grouping widget to a dashboard to change how charts are grouped by time. This widget won't filter the data; it'll change how Metabase displays the data. For example, you may want to look at the time series charts grouped by month by default, but give people the option to view the same results by other groupings: by week, by quarter, and so on. This widget doesn't filter data in the charts; the widget just changes the time granularity for any cards that have a datetime field connected to the widget. -You can group by: +Grouping options include: - Minute (or minute of hour) - Hour (or hour of day) @@ -87,6 +89,8 @@ You can group by: - Quarter (or quarter of year) - Year +To connect a time grouping widget to a SQL question, you'll need to insert time grouping parameters in your code. See [time grouping parameters](../questions/native-editor/time-grouping-parameters). + ## Location filters There are four types of Location filters to choose from: @@ -96,10 +100,21 @@ There are four types of Location filters to choose from: - ZIP or Postal Code - Country +Additionally, you can select an operator for the location filter: + +- **Is**. Select one or more values from a list or search box. Use **Is** when you just want to plug a value into a variable. For multiple values, the card must be either a question built using the query builder, or a native/SQL question using a [field filter](../questions/native-editor/sql-parameters#field-filter-variables). +- **Is not**. Exclude one or more specific values. +- **Contains**. Match values that contain the entered text. +- **Does not contain**. Filter out values that contain the entered text. +- **Starts with**. Match values that begin with the entered text. +- **Ends with**. Match values that end with the entered text. + ## ID filter The ID filter provides a simple input box where you can type the ID of a user, order, etc. +You can give people the option to pick one value or multiple values. + ## Number filter You can choose from: @@ -114,21 +129,25 @@ You can choose from: A flexible filter type that will let you create either a dropdown menu or an input box to filter on any category field in your cards. Options include: -- **Is**. Select one or more values from a list or search box. Use **Is** when you just want to plug a value into a variable. For multiple values, the card must be either a question built using the query builder, or a native/SQL question using a [field filter](../questions/native-editor/sql-parameters#the-field-filter-variable-type). +- **Is**. Select one or more values from a list or search box. Use **Is** when you just want to plug a value into a variable. For multiple values, the card must be either a question built using the query builder, or a native/SQL question using a [field filter](../questions/native-editor/sql-parameters#field-filter-variables). - **Is not**. Exclude one or more specific values. - **Contains**. Match values that contain the entered text. - **Does not contain**. Filter out values that contain the entered text. - **Starts with**. Match values that begin with the entered text. - **Ends with**. Match values that end with the entered text. +You can also select how people should filter on this column: + +- Dropdown list +- Search box +- Input box + ## Boolean filter A boolean filter allows people to filter data based on true/false values. ## Connecting a filter or parameter widget to dashboard cards -Dashboard widgets apply across all [dashboard tabs](./introduction#dashboard-tabs), though they'll only be displayed when a tab has cards connected to the widget. - For each widget that you add, you'll need to tell Metabase which column the filter should update for each card. Click on a card's dropdown menu to select the field that you want the widget to filter on. @@ -137,6 +156,11 @@ Here we've wired up a Text filter to the "Event types" card, telling Metabase th  +Which cards you can connect a filter or parameter widget to depends on: + +- Whether the question card has the relevant field. +- Where the widget is located: on the dashboard, heading card, or question card. Only dashboard widgets can be connected to cards across all [dashboard tabs](./introduction#dashboard-tabs). Widgets on heading and question cards are restricted to the cards on their respective tabs. + ## Auto-connecting filters to cards If there are other cards that also have the field you select, Metabase will offer to automatically connect the filter to those cards too (including to relevant cards on other tabs). If you later add a card with the selected field, Metabase will also try to connect that filter to the new card. @@ -145,9 +169,9 @@ To undo this auto-connecting of cards, click on the toast that pops up when Meta ## Filtering dashboards with native/SQL questions -If you're trying to connect a filter to a card with a native/SQL questions, you'll need to [add a variable or field filter to your query](../questions/native-editor/sql-parameters). For an in-depth article, check out [Adding filters to dashboards with SQL questions](/learn/metabase-basics/querying-and-dashboards/sql-in-metabase/filters). +For filters, you'll need to [add a variable or field filter to your query](../questions/native-editor/sql-parameters). -You can't connect a time grouping parameter widget to a card with a SQL question. +For parameters, check out [Time grouping parameters](../questions/native-editor/time-grouping-parameters). ## Wiring up dashboard filters to text cards diff --git a/_docs/master/dashboards/linked-filters.md b/_docs/master/dashboards/linked-filters.md index 50e9dd50e5..36737fdd16 100644 --- a/_docs/master/dashboards/linked-filters.md +++ b/_docs/master/dashboards/linked-filters.md @@ -63,7 +63,7 @@ Metabase uses database column metadata to populate values for linked filters, wh - You can't create linked filters on custom columns. -- Native/SQL questions must have a [field filter](../questions/native-editor/sql-parameters#the-field-filter-variable-type) variable in order to be linked. Basic SQL variables aren't connected to database columns, so they won't work for linked filters. +- Native/SQL questions must have a [field filter](../questions/native-editor/sql-parameters#field-filter-variables) variable in order to be linked. Basic SQL variables aren't connected to database columns, so they won't work for linked filters. - You can't link filters that use "Custom List" or "From another model or question" as their value's source. diff --git a/_docs/master/data-modeling/field-types.md b/_docs/master/data-modeling/field-types.md index 29a3103338..fbdd6a28c7 100644 --- a/_docs/master/data-modeling/field-types.md +++ b/_docs/master/data-modeling/field-types.md @@ -173,7 +173,7 @@ When you [X-ray](../exploration-and-organization/x-rays) a table, model, or enti ### Field Filters -Knowing what field types are and how they work is helpful when using [field filters](/learn/metabase-basics/querying-and-dashboards/sql-in-metabase/field-filters), as you can only create field filters for [certain field types](../questions/native-editor/sql-parameters#field-filter-compatible-types). +Knowing what field types are and how they work is helpful when using [field filters](/learn/metabase-basics/querying-and-dashboards/sql-in-metabase/field-filters), as you can only create field filters for [certain field types](../questions/native-editor/sql-parameters#field-filters-are-only-compatible-with-certain-types). ### JSON unfolding diff --git a/_docs/master/developers-guide/community-drivers.md b/_docs/master/developers-guide/community-drivers.md index 813138954b..2b13b29798 100644 --- a/_docs/master/developers-guide/community-drivers.md +++ b/_docs/master/developers-guide/community-drivers.md @@ -37,7 +37,7 @@ Anyone can build a community driver. These are the currently known third-party d | ------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- | | [CSV](https://github.com/Markenson/csv-metabase-driver) |  |  | | [Databend](https://github.com/databendcloud/metabase-databend-driver) |  |  | -| [DB2](https://github.com/damienchambe/metabase-db2-driver) |  |  | +| [DB2](https://github.com/damienchambe/metabase-db2-driver) |  |  | | [Dremio](https://github.com/Baoqi/metabase-dremio-driver) |  |  | | [DuckDB](https://github.com/MotherDuck-Open-Source/metabase_duckdb_driver) |  |  | | [Firebolt](https://github.com/firebolt-db/metabase-firebolt-driver) |  |  | diff --git a/_docs/master/developers-guide/devenv.md b/_docs/master/developers-guide/devenv.md index b5798dc53c..14d6002437 100644 --- a/_docs/master/developers-guide/devenv.md +++ b/_docs/master/developers-guide/devenv.md @@ -28,6 +28,8 @@ yarn dev This runs both the [frontend](#frontend) and [backend](#backend). Alternatively, you can run them separately in two terminal sessions below. +To use any other database beside the default ones please take a look at [Building Drivers](#building-drivers) further down in this document. + ### Frontend Metabase depends on third-party libraries to run, so you'll need to keep those up to date. The Clojure CLI will automatically fetch the dependencies when needed. With JavaScript dependencies, however, you'll need to kick off the installation process manually. diff --git a/_docs/master/developers-guide/frontend.md b/_docs/master/developers-guide/frontend.md index 1031ea7210..1e0630eef2 100644 --- a/_docs/master/developers-guide/frontend.md +++ b/_docs/master/developers-guide/frontend.md @@ -266,7 +266,7 @@ function getFoo(a, b, c) { } ``` -- Be conservative with what comments you add to the codebase. Comments shouldn't be used as reminders or as todos--record those by creating a new issue in Github. Ideally, code should be written in such a way that it explains itself clearly. When it does not, you should first try rewriting the code. If for whatever reason you are unable to write something clearly, add a comment to explain the "why". +- Be conservative with what comments you add to the codebase. Comments shouldn't be used as reminders or as todos--record those by creating a new issue in GitHub. Ideally, code should be written in such a way that it explains itself clearly. When it does not, you should first try rewriting the code. If for whatever reason you are unable to write something clearly, add a comment to explain the "why". ```javascript diff --git a/_docs/master/developers-guide/versioning.md b/_docs/master/developers-guide/versioning.md index 655d42cd76..82e02cc6d8 100644 --- a/_docs/master/developers-guide/versioning.md +++ b/_docs/master/developers-guide/versioning.md @@ -68,5 +68,5 @@ E.g., ## Further reading -- [Metabase releases on Github](https://github.com/metabase/metabase/releases) +- [Metabase releases on GitHub](https://github.com/metabase/metabase/releases) - [Metabase release blog posts](/releases) diff --git a/_docs/master/embedding/sdk/api/BaseInteractiveQuestionProps.html b/_docs/master/embedding/sdk/api/BaseInteractiveQuestionProps.html index 7effd3582a..70e4b609e9 100644 --- a/_docs/master/embedding/sdk/api/BaseInteractiveQuestionProps.html +++ b/_docs/master/embedding/sdk/api/BaseInteractiveQuestionProps.html @@ -9,7 +9,7 @@ layout: docs-api --- -
Optional
isOptional
onA callback function that triggers before saving. Only relevant when isSaveEnabled = true
Optional
onA callback function that triggers when a question is updated, including when a user clicks the Visualize
button in the question editor
Optional
onA callback function that triggers when a user saves the question. Only relevant when isSaveEnabled = true
Optional
onA callback function that triggers when a user saves the question. Only relevant when isSaveEnabled = true
Optional
pluginsThe ID of the question.
This is either:
diff --git a/_docs/master/embedding/sdk/api/CreateQuestion.html b/_docs/master/embedding/sdk/api/CreateQuestion.html
index 74327bd7e7..dd1d9a4f9b 100644
--- a/_docs/master/embedding/sdk/api/CreateQuestion.html
+++ b/_docs/master/embedding/sdk/api/CreateQuestion.html
@@ -14,7 +14,7 @@
Optional
isSaveEnabled?: booleanWhether to show the save button.
Optional
onBeforeSave?: (A callback function that triggers before saving. Only relevant when isSaveEnabled = true
Optional
onRun?: (question: undefined | MetabaseQuestion) => voidA callback function that triggers when a question is updated, including when a user clicks the Visualize
button in the question editor
Optional
onSave?: (A callback function that triggers when a user saves the question. Only relevant when isSaveEnabled = true
Optional
onSave?: (A callback function that triggers when a user saves the question. Only relevant when isSaveEnabled = true
Optional
plugins?: MetabasePluginsConfigOptional
targetCollection?: SdkCollectionIdThe collection to save the question to. This will hide the collection picker from the save modal. Only applicable to interactive questions.
Optional
withDownloads?: booleanEnables the ability to download results in the interactive question.
Use <InteractiveQuestion questionId="new" />
instead.
Optional
isWhether to show the save button.
Optional
onA callback function that triggers before saving. Only relevant when isSaveEnabled = true
Optional
onA callback function that triggers when a question is updated, including when a user clicks the Visualize
button in the question editor
Optional
onA callback function that triggers when a user saves the question. Only relevant when isSaveEnabled = true
Optional
onA callback function that triggers when a user saves the question. Only relevant when isSaveEnabled = true
Optional
pluginsOptional
targetThe collection to save the question to. This will hide the collection picker from the save modal. Only applicable to interactive questions.
Optional
withEnables the ability to download results in the interactive question.
Props for the drill-through question
-Optional
isWhether to show the save button.
Optional
onA callback function that triggers before saving. Only relevant when isSaveEnabled = true
Optional
onA callback function that triggers when a question is updated, including when a user clicks the Visualize
button in the question editor
Optional
onA callback function that triggers when a user saves the question. Only relevant when isSaveEnabled = true
Optional
onA callback function that triggers when a user saves the question. Only relevant when isSaveEnabled = true
Optional
pluginsOptional
styleA custom style object to be added to the root element.
Optional
targetThe collection to save the question to. This will hide the collection picker from the save modal. Only applicable to interactive questions.
Optional
titleDetermines whether the question title is displayed, and allows a custom title to be displayed instead of the default question title. Shown by default. Only applicable to interactive questions when using the default layout.
diff --git a/_docs/master/embedding/sdk/api/EditableDashboard.html b/_docs/master/embedding/sdk/api/EditableDashboard.html index 340dbcd435..43f5381000 100644 --- a/_docs/master/embedding/sdk/api/EditableDashboard.html +++ b/_docs/master/embedding/sdk/api/EditableDashboard.html @@ -9,13 +9,9 @@ layout: docs-api --- -A dashboard component with the features available in the InteractiveDashboard
component, as well as the ability to add and update questions, layout, and content within your dashboard.
Optional
drillThroughQuestionHeight?: Height<string | number>Height of a question component when drilled from the dashboard to a question level.
-Optional
drillThroughQuestionProps?: DrillThroughQuestionPropsProps of a question component when drilled from the dashboard to a question level.
-Optional
plugins?: MetabasePluginsConfigAdditional mapper function to override or add drill-down menu. See the implementing custom actions section for more details.
-Optional
renderDrillThroughQuestion?: () => ReactNodeA custom React component to render the question layout. -Use namespaced InteractiveQuestion components to build the layout.
-The ID of the dashboard. +
A dashboard component with the features available in the InteractiveDashboard
component, as well as the ability to add and update questions, layout, and content within your dashboard.
Optional
className?: stringA custom class name to be added to the root element.
+The ID of the dashboard.
This is either:
entity_id
key of the dashboard object when using the API directly or using the SDK Collection Browser to return dataOptional
hiddenParameters?: string[]A list of parameters to hide. +
Optional
dataPickerProps?: Pick<InteractiveQuestionProps, "entityTypes">Additional props to pass to the query builder rendered by InteractiveQuestion
when creating a new dashboard question.
Optional
drillThroughQuestionHeight?: Height<string | number>Height of a question component when drilled from the dashboard to a question level.
+Optional
drillThroughQuestionProps?: DrillThroughQuestionPropsProps of a question component when drilled from the dashboard to a question level.
+Optional
hiddenParameters?: string[]A list of parameters to hide.
Optional
initialParameters?: ParameterValuesQuery parameters for the dashboard. For a single option, use a string
value, and use a list of strings for multiple options.
+
Optional
initialParameters?: ParameterValuesQuery parameters for the dashboard. For a single option, use a string
value, and use a list of strings for multiple options.
Optional
withCardTitle?: booleanWhether the dashboard cards should display a title.
-Optional
withDownloads?: booleanWhether to hide the download button.
-Optional
withTitle?: booleanWhether the dashboard should display a title.
-Optional
className?: stringA custom class name to be added to the root element.
-Optional
style?: CSSPropertiesA custom style object to be added to the root element.
-Optional
onLoad?: (dashboard: null | MetabaseDashboard) => voidCallback that is called when the dashboard is loaded.
-Optional
onLoadWithoutCards?: (dashboard: null | MetabaseDashboard) => voidCallback that is called when the dashboard is loaded without cards.
-Optional
onLoad?: (dashboard: null | MetabaseDashboard) => voidCallback that is called when the dashboard is loaded.
+Optional
onLoadWithoutCards?: (dashboard: null | MetabaseDashboard) => voidCallback that is called when the dashboard is loaded without cards.
+Optional
plugins?: MetabasePluginsConfigAdditional mapper function to override or add drill-down menu. See the implementing custom actions section for more details.
+Optional
renderDrillThroughQuestion?: () => ReactNodeA custom React component to render the question layout. +Use namespaced InteractiveQuestion components to build the layout.
+Optional
style?: CSSPropertiesA custom style object to be added to the root element.
+Optional
withCardTitle?: booleanWhether the dashboard cards should display a title.
+Optional
withDownloads?: booleanWhether to hide the download button.
+Optional
withTitle?: booleanWhether the dashboard should display a title.
+entity_id
key of the dashboard object when using the API directly or using the SDK Collection Browser to return dataOptional
dataAdditional props to pass to the query builder rendered by InteractiveQuestion
when creating a new dashboard question.
Optional
drillHeight of a question component when drilled from the dashboard to a question level.
Optional
drillProps of a question component when drilled from the dashboard to a question level.
Props for the drill-through question
@@ -44,7 +46,7 @@Optional
isSaveEnabled?: booleanWhether to show the save button.
Optional
onBeforeSave?: (A callback function that triggers before saving. Only relevant when isSaveEnabled = true
Optional
onRun?: (question: undefined | MetabaseQuestion) => voidA callback function that triggers when a question is updated, including when a user clicks the Visualize
button in the question editor
Optional
onSave?: (A callback function that triggers when a user saves the question. Only relevant when isSaveEnabled = true
Optional
onSave?: (A callback function that triggers when a user saves the question. Only relevant when isSaveEnabled = true
Optional
plugins?: MetabasePluginsConfigOptional
style?: CSSPropertiesA custom style object to be added to the root element.
Optional
targetCollection?: SdkCollectionIdThe collection to save the question to. This will hide the collection picker from the save modal. Only applicable to interactive questions.
Optional
title?: SdkQuestionTitlePropsDetermines whether the question title is displayed, and allows a custom title to be displayed instead of the default question title. Shown by default. Only applicable to interactive questions when using the default layout.
@@ -75,4 +77,4 @@Optional
withWhether the dashboard cards should display a title.
Optional
withWhether to hide the download button.
Optional
withWhether the dashboard should display a title.
-A dashboard component with drill downs, click behaviors, and the ability to view and click into questions.
-Optional
drillThroughQuestionHeight?: Height<string | number>Height of a question component when drilled from the dashboard to a question level.
+A dashboard component with drill downs, click behaviors, and the ability to view and click into questions.
+Optional
drillThroughQuestionHeight?: Height<string | number>Height of a question component when drilled from the dashboard to a question level.
Optional
drillThroughQuestionProps?: DrillThroughQuestionPropsProps of a question component when drilled from the dashboard to a question level.
Optional
plugins?: MetabasePluginsConfigAdditional mapper function to override or add drill-down menu. See the implementing custom actions section for more details.
Optional
renderDrillThroughQuestion?: () => ReactNodeA custom React component to render the question layout. @@ -45,4 +45,5 @@
Optional
style?: CSSPropertiesA custom style object to be added to the root element.
Optional
onLoad?: (dashboard: null | MetabaseDashboard) => voidCallback that is called when the dashboard is loaded.
Optional
onLoadWithoutCards?: (dashboard: null | MetabaseDashboard) => voidCallback that is called when the dashboard is loaded without cards.
+Optional
dataPickerProps?: Pick<InteractiveQuestionProps, "entityTypes">Additional props to pass to the query builder rendered by InteractiveQuestion
when creating a new dashboard question.
entity_id
key of the dashboard object when using the API directly or using the SDK Collection Browser to return dataOptional
dataAdditional props to pass to the query builder rendered by InteractiveQuestion
when creating a new dashboard question.
Optional
drillHeight of a question component when drilled from the dashboard to a question level.
Optional
drillProps of a question component when drilled from the dashboard to a question level.
Props for the drill-through question
@@ -44,7 +46,7 @@Optional
isSaveEnabled?: booleanWhether to show the save button.
Optional
onBeforeSave?: (A callback function that triggers before saving. Only relevant when isSaveEnabled = true
Optional
onRun?: (question: undefined | MetabaseQuestion) => voidA callback function that triggers when a question is updated, including when a user clicks the Visualize
button in the question editor
Optional
onSave?: (A callback function that triggers when a user saves the question. Only relevant when isSaveEnabled = true
Optional
onSave?: (A callback function that triggers when a user saves the question. Only relevant when isSaveEnabled = true
Optional
plugins?: MetabasePluginsConfigOptional
style?: CSSPropertiesA custom style object to be added to the root element.
Optional
targetCollection?: SdkCollectionIdThe collection to save the question to. This will hide the collection picker from the save modal. Only applicable to interactive questions.
Optional
title?: SdkQuestionTitlePropsDetermines whether the question title is displayed, and allows a custom title to be displayed instead of the default question title. Shown by default. Only applicable to interactive questions when using the default layout.
@@ -75,4 +77,4 @@Optional
withWhether the dashboard cards should display a title.
Optional
withWhether to hide the download button.
Optional
withWhether the dashboard should display a title.
-Optional
isSaveEnabled?: booleanWhether to show the save button.
Optional
onBeforeSave?: (A callback function that triggers before saving. Only relevant when isSaveEnabled = true
Optional
onRun?: (question: undefined | MetabaseQuestion) => voidA callback function that triggers when a question is updated, including when a user clicks the Visualize
button in the question editor
Optional
onSave?: (A callback function that triggers when a user saves the question. Only relevant when isSaveEnabled = true
Optional
onSave?: (A callback function that triggers when a user saves the question. Only relevant when isSaveEnabled = true
Optional
plugins?: MetabasePluginsConfigThe ID of the question.
This is either:
diff --git a/_docs/master/embedding/sdk/api/InteractiveQuestionProps.html b/_docs/master/embedding/sdk/api/InteractiveQuestionProps.html
index f95a95d61b..ab3d118292 100644
--- a/_docs/master/embedding/sdk/api/InteractiveQuestionProps.html
+++ b/_docs/master/embedding/sdk/api/InteractiveQuestionProps.html
@@ -9,7 +9,7 @@
layout: docs-api
---
-
Optional
isWhether to show the save button.
Optional
onA callback function that triggers before saving. Only relevant when isSaveEnabled = true
Optional
onA callback function that triggers when a question is updated, including when a user clicks the Visualize
button in the question editor
Optional
onA callback function that triggers when a user saves the question. Only relevant when isSaveEnabled = true
Optional
onA callback function that triggers when a user saves the question. Only relevant when isSaveEnabled = true
Optional
pluginsThe ID of the question.
This is either:
diff --git a/_docs/master/embedding/sdk/api/StaticDashboard.html b/_docs/master/embedding/sdk/api/StaticDashboard.html
index b2934e2415..137b9f13ef 100644
--- a/_docs/master/embedding/sdk/api/StaticDashboard.html
+++ b/_docs/master/embedding/sdk/api/StaticDashboard.html
@@ -9,8 +9,8 @@
layout: docs-api
---
-
A lightweight dashboard component.
-Optional
drillThroughQuestionHeight?: Height<string | number>Height of a question component when drilled from the dashboard to a question level.
+A lightweight dashboard component.
+Optional
drillThroughQuestionHeight?: Height<string | number>Height of a question component when drilled from the dashboard to a question level.
Optional
drillThroughQuestionProps?: DrillThroughQuestionPropsProps of a question component when drilled from the dashboard to a question level.
Optional
plugins?: MetabasePluginsConfigAdditional mapper function to override or add drill-down menu. See the implementing custom actions section for more details.
Optional
renderDrillThroughQuestion?: () => ReactNodeA custom React component to render the question layout. @@ -45,4 +45,5 @@
Optional
style?: CSSPropertiesA custom style object to be added to the root element.
Optional
onLoad?: (dashboard: null | MetabaseDashboard) => voidCallback that is called when the dashboard is loaded.
Optional
onLoadWithoutCards?: (dashboard: null | MetabaseDashboard) => voidCallback that is called when the dashboard is loaded without cards.
+Optional
dataPickerProps?: Pick<InteractiveQuestionProps, "entityTypes">Additional props to pass to the query builder rendered by InteractiveQuestion
when creating a new dashboard question.
entity_id
key of the dashboard object when using the API directly or using the SDK Collection Browser to return dataOptional
dataAdditional props to pass to the query builder rendered by InteractiveQuestion
when creating a new dashboard question.
Optional
drillHeight of a question component when drilled from the dashboard to a question level.
Optional
drillProps of a question component when drilled from the dashboard to a question level.
Props for the drill-through question
@@ -44,7 +46,7 @@Optional
isSaveEnabled?: booleanWhether to show the save button.
Optional
onBeforeSave?: (A callback function that triggers before saving. Only relevant when isSaveEnabled = true
Optional
onRun?: (question: undefined | MetabaseQuestion) => voidA callback function that triggers when a question is updated, including when a user clicks the Visualize
button in the question editor
Optional
onSave?: (A callback function that triggers when a user saves the question. Only relevant when isSaveEnabled = true
Optional
onSave?: (A callback function that triggers when a user saves the question. Only relevant when isSaveEnabled = true
Optional
plugins?: MetabasePluginsConfigOptional
style?: CSSPropertiesA custom style object to be added to the root element.
Optional
targetCollection?: SdkCollectionIdThe collection to save the question to. This will hide the collection picker from the save modal. Only applicable to interactive questions.
Optional
title?: SdkQuestionTitlePropsDetermines whether the question title is displayed, and allows a custom title to be displayed instead of the default question title. Shown by default. Only applicable to interactive questions when using the default layout.
@@ -75,4 +77,4 @@Optional
withWhether the dashboard cards should display a title.
Optional
withWhether to hide the download button.
Optional
withWhether the dashboard should display a title.
-Optional
style?: CSSPropertiesA custom style object to be added to the root element.
Optional
width?: Width<string | number>A number or string specifying a CSS size value that specifies the width of the component
-Optional
withChartTypeSelector?: booleanOptional
withChartTypeSelector?: booleanOptional
withDownloads?: booleanEnables the ability to download results in the interactive question.
+Optional
classA custom class name to be added to the root element.
Optional
heightA number or string specifying a CSS size value that specifies the height of the component
Optional
initialInitial values for the SQL parameters.
@@ -32,4 +33,5 @@Optional
styleA custom style object to be added to the root element.
Optional
widthA number or string specifying a CSS size value that specifies the width of the component
-Optional
withOptional
withOptional
withEnables the ability to download results in the interactive question.
+
Whether to show the save button.