You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _docs/master/dashboards/filters.md
+31-31Lines changed: 31 additions & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,11 +16,11 @@ redirect_from:
16
16
17
17

18
18
19
-
Instead of creating duplicate dashboards to show different cuts of the same data (like a different dashboard for each quarter), you can add filter or parameter widgets to let people change _what_ data is displayed (filter the data), or _how_it's displayed (parameterize the data).
19
+
Instead of creating duplicate dashboards to show different cuts of the same data (like a different dashboard for each quarter), you can add filter or parameter widgets to let people change _what_ data is displayed (filter the data), or _how_its displayed (parameterize the data).
20
20
21
21
## Filter and parameter widgets
22
22
23
-
There are two basic types of widgets you can add. The type of filter or parameter widget you choose determines how the widget works, including which fields you can connect to the widget.
23
+
There are two basic types of widgets you can add. The type of filter or parameter widget you choose determines how the widget works, including which fields you'll can connect to the widget.
24
24
25
25
### Filter widgets
26
26
@@ -57,7 +57,7 @@ There are two basic types of widgets you can add. The type of filter or paramete
57
57
5.[Configure your filter](#editing-a-filter).
58
58
6.**Save** your changes.
59
59
60
-
If the filter isn't connected to any of the cards on the current tab, Metabase won't display the filter.
60
+
If the filter isn't connected any of the cards on the current tab, Metabase won't display the filter.
61
61
62
62
### When to add a widget to a heading or card
63
63
@@ -83,11 +83,11 @@ When picking a Date picker filter, Metabase will prompt you to pick an operator:
83
83
- Relative Date
84
84
- All Options
85
85
86
-
Single Date and Date Range will provide a calendar widget, while the other options 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".
86
+
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.
87
87
88
88
### Issues with connecting to a date variable
89
89
90
-
If you get a message like "A date variable in this card can only be connected to a time type with the Single date option," you can handle it in a couple of ways.
90
+
If you get a message like "A date variable in this card can only be connectedd to a time type with the single date option", you can handle it in a couple of ways.
91
91
92
92
-**If you want a date picker where people can select multiple dates**, you'll need to change the variable in your SQL code to a [field filter](../questions/native-editor/field-filters).
93
93
-**If you want the filter widget to just take a single date**, you'll need to change the dashboard filter widget's type to "Single date".
@@ -132,7 +132,7 @@ Additionally, you can select an operator for the location filter:
132
132
133
133
## ID filter
134
134
135
-
The ID filter provides a simple input box where you can type the ID of a user, order, and so on.
135
+
The ID filter provides a simple input box where you can type the ID of a user, order, etc.
136
136
137
137
You can give people the option to pick one value or multiple values.
138
138
@@ -148,7 +148,7 @@ You can choose from:
148
148
149
149
## Text or category filter
150
150
151
-
A flexible filter type that lets you create either a dropdown menu or an input box to filter on any text or category field in your cards. Options include:
151
+
A flexible filter type that will let you create either a dropdown menu or an input box to filter on any text or category field in your cards. Options include:
152
152
153
153
-**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 a question built using the query builder, a native/SQL question using a [field filter](../questions/native-editor/field-filters), or a basic variable set to [multiple values](../questions/native-editor/basic-sql-parameters#basic-variable-that-allows-people-to-select-multiple-values).
154
154
-**Is not**. Exclude one or more specific values.
@@ -171,9 +171,9 @@ A boolean filter allows people to filter data based on true/false values.
171
171
172
172
For each widget that you add, you'll need to tell Metabase which column the filter should update for each card.
173
173
174
-
Click a card's dropdown menu to select the field that you want the widget to filter on.
174
+
Click on a card's dropdown menu to select the field that you want the widget to filter on.
175
175
176
-
Here we've wired up a text filter to the "Event types" card, telling Metabase that the column to filter on should be the `Analytics.Event.Button.Label` field:
176
+
Here we've wired up a Text filter to the "Event types" card, telling Metabase that the column to filter on should be the `Analytics.Event.Button.Label` field:
177
177
178
178

179
179
@@ -182,17 +182,17 @@ Which cards you can connect a filter or parameter widget to depends on:
182
182
- Whether the card has a relevant field (i.e., the field the widget is filtering).
183
183
- 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.
184
184
185
-
## Filtering dashboards with native/SQL questions
185
+
## Auto-connecting filters to cards
186
186
187
-
To connect a dashboard filter widget to a card with a question created with the native editor, you'll need to [add a field filter or basic variable to your query](../questions/native-editor/sql-parameters).
187
+
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.
188
188
189
-
For parameters, check out [Time grouping parameters](../questions/native-editor/time-grouping-parameters).
189
+
To undo this auto-connecting of cards, click on the toast that pops up when Metabase auto-connects the cards, or manually disconnect the cards by clicking on the "X" next to the connected field.
190
190
191
-
## Auto-connecting filters to cards
191
+
## Filtering dashboards with native/SQL questions
192
192
193
-
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 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.
193
+
For filters, you'll need to [add a variable or fieldfilter to your query](../questions/native-editor/sql-parameters).
194
194
195
-
To undo this auto-connecting of cards, click the notification that pops up when Metabase auto-connects the cards, or manually disconnect the cards by clicking the "X" next to the connected field.
195
+
For parameters, check out [Time grouping parameters](../questions/native-editor/time-grouping-parameters).
196
196
197
197
## Wiring up dashboard filters to text cards
198
198
@@ -209,10 +209,10 @@ You might want to require a filter value if:
209
209
210
210
## Editing a filter
211
211
212
-
To edit a dashboard filter's settings:
212
+
To edit a filter's settings:
213
213
214
214
1. Click the **pencil** icon to enter dashboard editing mode.
215
-
2. Click the filter you want to edit.
215
+
2. Click the **gear** icon on the filter you want to edit.
216
216
217
217
From this filter editing view, you can wire up dashboard cards to the filter, or use the filter settings sidebar to:
218
218
@@ -226,14 +226,14 @@ From this filter editing view, you can wire up dashboard cards to the filter, or
226
226
227
227
### Rename filter
228
228
229
-
1. In dashboard edit mode, click the filter you want to edit.
229
+
1. In dashboard edit mode, click your filter's **gear** icon.
230
230
2. Change the label text.
231
231
232
232
Renaming the filter only affects the filter's display; the label has no effect on which columns Metabase filters.
233
233
234
234
### Set filter input type
235
235
236
-
1. In dashboard edit mode, click the filter you want to edit.
236
+
1. In dashboard edit mode, click your filter's **gear** icon.
237
237
2. From the filter settings sidebar, set **How should people filter on this column?**:
238
238
239
239
-[Dropdown list](#dropdown-list)
@@ -242,9 +242,9 @@ Renaming the filter only affects the filter's display; the label has no effect o
242
242
243
243
#### Dropdown list
244
244
245
-
A list of all the possible values in a column. People can use checkboxes to select more than one value on [multi-select filters](#make-a-multi-select-filter). If you want the list of filter values to load instantly (from cache), you should choose the dropdown widget.
245
+
A list of all of the possible values in a column. People can use checkboxes to select more than one value on [multi-select filters](#make-a-multi-select-filter). You should choose the dropdown widget if you want the list of filter values to load instantly (from cache).
246
246
247
-
If you're not seeing the **Dropdown list** option and your dashboard filter is based on a column from a:
247
+
If you're not seeing the **Dropdown list** option, and your dashboard filter is based on a column from a:
248
248
249
249
- Table or model built with the query builder: an admin will need to [enable the dropdown widget](../data-modeling/metadata-editing#changing-a-search-box-filter-to-a-dropdown-filter) for that column from Metabase's **Admin settings**.
250
250
- Model built with a SQL query: go to your [model's metadata settings](../data-modeling/models#add-metadata-to-columns-in-a-model), find your column, and set the **Database column this maps to**.
@@ -253,7 +253,7 @@ If you're not seeing the **Dropdown list** option and your dashboard filter is b
253
253
254
254
A search box that suggests a list of matching filter values as you type. The suggestion list will display checkboxes for [multi-select filters](#make-a-multi-select-filter).
255
255
256
-
The search box is a good choice for most columns containing labels, categories, statuses, and so on. It's the default filter widget for columns with fewer than 100 unique values.
256
+
The search box is a good choice for most columns containing labels, categories, statuses, and so on. It's is the default filter widget for columns with less than 100 unique values.
257
257
258
258
#### Plain input box
259
259
@@ -263,32 +263,32 @@ Useful for looking up partial matches (such as the ["contains" filter](#text-or-
263
263
264
264
### Set a default filter value
265
265
266
-
1. In dashboard edit mode, click the filter you want to edit.
266
+
1. In dashboard edit mode, click your filter's **gear** icon.
267
267
2. From the sidebar, choose a value from the **Default value** input field.
268
268
269
-
For example, you might want to set a default filter value like "Active," so that when people load your dashboard, they only see data for "Active" records (not "Inactive," "Canceled," and so on).
269
+
For example, you might want to set a default filter value like "Active", so that when people load your dashboard, they only see data for "Active" records (not "Inactive", "Cancelled", etc).
270
270
271
271
### Remove a filter
272
272
273
-
1. In dashboard edit mode, click the filter you want to edit.
273
+
1. In dashboard edit mode, click your filter's **gear** icon.
274
274
2. From the sidebar, click **Remove**.
275
275
276
276
If you accidentally remove a filter, just click **Cancel** in the top-right to exit dashboard edit mode without saving your changes.
277
277
278
278
### Reorder filters
279
279
280
-
In dashboard edit mode, click the grabber handle (six dots) on the left side of a filter widget, then drag the widget to a different position.
280
+
In dashboard edit mode, click on the grabber handle (six dots) on the left side of a filter widget, then drag the widget to a different position.
281
281
282
282
### Make a multi-select filter
283
283
284
-
1. In dashboard edit mode, click the filter you want to edit.
284
+
1. In dashboard edit mode, click your filter's **gear** icon.
285
285
2. From the sidebar, find **People can pick** and select "Multiple values".
286
286
287
287
A multi-select filter with the widget type [Dropdown list](#dropdown-list) or [Search box](#search-box) will display a list of values with checkboxes.
288
288
289
289
### Change a filter's selectable values
290
290
291
-
1. In dashboard edit mode, click the filter you want to edit.
291
+
1. In dashboard edit mode, click your filter's **gear** icon.
292
292
2. From the sidebar, find **How should users filter on this column?**.
293
293
3. Select "Dropdown list".\*
294
294
4. Click **Edit** (to the right of "Dropdown list") to specify where the values should come from:
@@ -310,9 +310,9 @@ By default, each time you change the value in a filter on a dashboard, the dashb
310
310
311
311
If a dashboard is particularly large or slow, or you have multiple filters that you want to adjust before the dashboard refreshes its results, you may want to tell Metabase when to apply those filters and refresh the dashboard.
312
312
313
-
To turn off the automatic application of filters:
313
+
To turn off the automatic application of filters.
314
314
315
-
1.View the dashboard (not in edit mode) and click the three-dot menu **...**.
315
+
1.Click on the three-dot menu **...**.
316
316
2. Select **Edit settings**.
317
317
3. In the **General** section, toggle off **Auto-apply filters**.
318
318
@@ -322,7 +322,7 @@ With auto-apply turned off, each time you change a value in a filter, you'll nee
322
322
323
323
## Using filter widgets
324
324
325
-
Once you've added a filter to your dashboard, click the filter widget to select a value and activate the filter. To stop filtering, click the blue X.
325
+
Once you've added a filter to your dashboard, just click on the filter widget to select a value and activate the filter. To stop filtering, just click the blue X.
326
326
327
327
Your active filter will only apply to your view of the dashboard. If someone else is viewing the same dashboard link at the same time, they won't see your filter.
Copy file name to clipboardExpand all lines: _docs/master/data-modeling/json-unfolding.md
+4-7Lines changed: 4 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,11 +73,8 @@ For example, if you upload a CSV with JSON in it, you might need to update the d
73
73
74
74
## Databases that support JSON unfolding
75
75
76
-
-[BigQuery](../databases/connections/postgresql): automatically enabled, applies to `STRUCT` types only.
77
-
78
-
If your data is stored in the [STRUCT data type](https://cloud.google.com/bigquery/docs/reference/standard-sql/data-types#struct_type) in BigQuery, you can query the table's nested fields. This is enabled by default. However, Metabase won't unfold JSON stored in BigQuery as the `JSON` type. This is because in BigQuery, nested fields are _part of the table definition itself_, so when Metabase syncs with your BigQuery database, it'll be able to get metadata about any of your tables, including tables with nested fields. Querying nested fields, however, doesn't extend to arrays (REPEATED (STRUCT)) in BigQuery.
79
-
80
-
-[Druid (JDBC)](../databases/connections/druid)
81
-
-[MongoDB](../databases/connections/mysql): automatically enabled for all nested fields.
A note on [BigQuery](../databases/connections/bigquery): Metabase supports the [STRUCT data type](https://cloud.google.com/bigquery/docs/reference/standard-sql/data-types#struct_type) in BigQuery, but it won't unfold JSON stored in BigQuery as the `JSON` type. If your data is stored in the `STRUCT` type in BigQuery, you can query the table's nested fields. Some background here: BigQuery differs from other databases in that nested fields are _part of the table definition itself_. So when Metabase syncs with your BigQuery database, it'll be able to get metadata about any of your tables, including tables with nested fields. Querying nested fields, however, doesn't extend to arrays (REPEATED (STRUCT)) in BigQuery.
Copy file name to clipboardExpand all lines: _docs/master/databases/connections/athena.md
-8Lines changed: 0 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -216,14 +216,6 @@ If Metabase also needs to create tables, you'll need additional AWS Glue permiss
216
216
217
217
There aren't (yet) any model features available for Athena.
218
218
219
-
## Database routing
220
-
221
-
With database routing, an admin can build a question once using a single data connection, and the question will run its query against a different data connection with the same schema depending on who is viewing the question.
222
-
223
-
Admittedly, the name "database routing" is misleading for Athena, because the term "database" in Athena is closer to "schema" in other databases. You _can't_ use database routing to route queries between different _databases_ in Athena, but you _can_ route between different data _connections_, e.g., different regions or buckets, or different IAM users, or different data sources/catalogs.
224
-
225
-
See [Database routing](../../permissions/database-routing).
Copy file name to clipboardExpand all lines: _docs/master/databases/connections/bigquery.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -170,8 +170,6 @@ There aren't (yet) any model features available for BigQuery.
170
170
171
171
## Database routing
172
172
173
-
With database routing, an admin can build a question once using one database, and the question will run its query against a different database with the same schema depending on who is viewing the question.
174
-
175
173
Database routing for BigQuery works between BigQuery **projects** with identical schemas.
176
174
177
175
See [Database routing](../../permissions/database-routing).
Copy file name to clipboardExpand all lines: _docs/master/databases/connections/databricks.md
-8Lines changed: 0 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -108,14 +108,6 @@ A fingerprinting query examines the first 10,000 rows from each column and uses
108
108
109
109
There aren't (yet) any model features available for Databricks.
110
110
111
-
## Database routing
112
-
113
-
With database routing, an admin can build a question once using one database, and the question will run its query against a different database with the same schema depending on who is viewing the question.
114
-
115
-
When **multi-catalog is not enabled**, you can route between catalogs on the same host. If multi-catalog is enabled, then you can only route between databases on separate hosts.
116
-
117
-
See [Database routing](../../permissions/database-routing).
0 commit comments