Skip to content

Commit 05924d0

Browse files
authored
docs: refresh dashboard filter requirement screenshots (#1031)
1 parent 4ee4b15 commit 05924d0

7 files changed

Lines changed: 2 additions & 2 deletions

guides/limiting-data-using-filters.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -331,7 +331,7 @@ While editing the dashboard, open the `Payment method` filter's popover and swit
331331
The "Order status *or* Order date" half of our example needs a requirement group. Open the **Filter rules** popover next to the filter bar, where you can manage every rule in one place:
332332

333333
1. Click **Add another rule**, pick `Order status`, then add `Order date` to the same rule. One filter makes a plain required filter; more make an "at least one of" group. Filters with a default value, or already in another rule, can't be picked.
334-
2. Optionally, write a **Note for viewers** explaining why the filters are required. Ours says: "This dashboard queries all historic orders. Pick a payment method, plus an order status or date range, to keep it fast."
334+
2. Optionally, write a **Note for viewers** explaining why the filters are required. Ours says: "Pick a payment method, plus an order status or date range, to keep this dashboard fast."
335335
3. Click **Save** in the popover, then save the dashboard.
336336

337337
<Frame>
@@ -376,7 +376,7 @@ Here's the same example in dashboard YAML: a required filter has `required: true
376376

377377
```yaml
378378
config:
379-
requiredFiltersNote: "This dashboard queries all historic orders. Pick a payment method, plus an order status or date range, to keep it fast."
379+
requiredFiltersNote: "Pick a payment method, plus an order status or date range, to keep this dashboard fast."
380380
filters:
381381
dimensions:
382382
- id: payment-method-filter
87.1 KB
Loading
91.1 KB
Loading
21.3 KB
Loading
22.5 KB
Loading
36.5 KB
Loading
38.2 KB
Loading

0 commit comments

Comments
 (0)