Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit 55428b4

Browse files
Documentation edits made through Mintlify web editor
1 parent fb1c188 commit 55428b4

File tree

1 file changed

+8
-9
lines changed

1 file changed

+8
-9
lines changed

‎guides/using-parameters.mdx

Lines changed: 8 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -3,11 +3,11 @@ title: "How to use parameters"
33
---
44

55
<Warning>
6-
Parameters are an **experimental** feature. See our [Feature Maturity Levels](/references/feature-maturity-levels) documentation to understand what this means.
6+
Parameters are an **experimental** feature. See our [Feature Maturity Levels](/references/feature-maturity-levels) documentation to understand what this means.
77
</Warning>
88

99
<Info>
10-
Parameters are defined in the `lightdash.config.yml` file, which is not supported when your project is connected to dbt Cloud.
10+
Parameters are defined in the `lightdash.config.yml` file, which is not supported when your project is connected to dbt Cloud.
1111
</Info>
1212

1313
**Parameters** are variables that allow you to create **dynamic, reusable queries** in Lightdash. They enable users to interact with and customize queries without needing to write SQL.
@@ -199,10 +199,9 @@ WHERE region IN (${lightdash.parameters.region})
199199

200200
This query will filter orders by the regions selected in the `region` parameter and by the date selected in the `date_range` parameter.
201201

202-
203202
## Saving parameter values at chart and dashboard levels
204203

205-
One of the powerful features of parameters is that their values can be saved at both the chart and dashboard levels.
204+
Parameter values can be saved at both the chart and dashboard levels.
206205

207206
### Saving parameter values in charts
208207

@@ -218,16 +217,16 @@ The parameter values will be saved with the chart and will be applied whenever t
218217

219218
### Saving parameter values in dashboards
220219

221-
You can also save parameter values at the dashboard level, which allows you to create dashboards with consistent filtering across all charts.
220+
You can also save parameter values at the dashboard level, which allows you to create dashboards with consistent parameter values across all charts.
222221

223-
To save parameter values with a dashboard:
222+
To save parameter values in a dashboard:
224223

225224
1. Create or edit a dashboard
226225
2. Add charts to the dashboard
227226
3. Set the parameter values as desired
228227
4. Save the dashboard
229228

230-
The parameter values will be saved with the dashboard and will be applied to all charts on the dashboard.
229+
The parameter values will be saved with the dashboard and will be applied to all charts on the dashboard that have parameterized fields.
231230

232231
## Best practices for using parameters
233232

@@ -236,5 +235,5 @@ Here are some best practices to follow when using parameters:
236235
1. **Use descriptive names**: Choose parameter names that clearly indicate their purpose
237236
2. **Provide default values**: Set default values for parameters to ensure queries work even if users don't set parameter values
238237
3. **Add descriptions**: Include clear descriptions for parameters to help users understand their purpose
239-
5. **Consider using options_from_dimension**: For parameters that should match values in your data, use `options_from_dimension` to dynamically populate options
240-
6. **Consider performance**: Be mindful of how parameters affect query performance, especially with large datasets
238+
4. **Consider using options_from_dimension**: For parameters that should match values in your data, use `options_from_dimension` to dynamically populate options
239+
5. **Consider performance**: Be mindful of how parameters affect query performance, especially with large datasets

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /