From e355143bbe09aa3384c523d3f693710015041c47 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Thu, 12 Feb 2026 19:49:51 +0000 Subject: [PATCH 1/7] Update guides/formatting-your-fields.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> --- guides/formatting-your-fields.mdx | 32 +++++++++++++++---------------- 1 file changed, 16 insertions(+), 16 deletions(-) diff --git a/guides/formatting-your-fields.mdx b/guides/formatting-your-fields.mdx index 06e6228c..bc047bdc 100644 --- a/guides/formatting-your-fields.mdx +++ b/guides/formatting-your-fields.mdx @@ -32,7 +32,7 @@ In your dbt YAML file, it'll look something like this: hidden: true ``` - + ```yaml models: - name: users @@ -72,7 +72,7 @@ The same thing goes for metrics: hidden: true ``` - + ```yaml models: - name: users @@ -158,7 +158,7 @@ For example you might want to group the percentile metrics into two sub categori groups: ['percentile', 'over'] ``` - + ```yaml models: - name: events @@ -272,7 +272,7 @@ By default, Lightdash pulls in the descriptions you've included for your dimensi description: 'Unique identifier for a user' ``` - + ```yaml models: - name: users @@ -322,7 +322,7 @@ If you don't add a custom description for your metric, Lightdash will show a des description: 'Count the unique number of user IDs' ``` - + ```yaml models: - name: users @@ -377,7 +377,7 @@ So, if I had a field `user_id_sha64`, I could relabel it to `User ID`. label: 'User ID' ``` - + ```yaml models: - name: users @@ -421,7 +421,7 @@ Same thing goes for metrics! label: 'Total users' ``` - + ```yaml models: - name: users @@ -484,7 +484,7 @@ Like this: format: '0.00' ``` - + ```yaml models: - name: sales @@ -527,7 +527,7 @@ Like this: format: '0.00' ``` - + ```yaml models: - name: sales @@ -588,7 +588,7 @@ Like this: format: '0," K"' ``` - + ```yaml models: - name: sales @@ -634,7 +634,7 @@ Like this: format: '0.00,,," B"' ``` - + ```yaml models: - name: sales @@ -698,7 +698,7 @@ You can add a `format` to your dimensions this: format: '[$£]#,##0.00' ``` - + ```yaml models: - name: sales @@ -742,7 +742,7 @@ You can add a `format` to your metrics this: format: '[$£]#,##0.00' ``` - + ```yaml models: - name: sales @@ -819,7 +819,7 @@ In your model YAML file: format: '${ld.parameters.currency_symbol}0,0.00' ``` - + ```yaml models: - name: sales @@ -898,7 +898,7 @@ In your model YAML file: format: '${ld.parameters.currency=="usd"?"$":""}${ld.parameters.currency=="eur"?"€":""}${ld.parameters.currency=="eur"?"£":""}0,0.00' ``` - + ```yaml models: - name: sales @@ -967,7 +967,7 @@ Then use it in your model YAML file: format: '0,0${ld.parameters.decimals=="true"?".00":""}' ``` - + ```yaml models: - name: sales From 5156cf8115865c29ccf962448cb0264d62fd8743 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Thu, 12 Feb 2026 19:50:00 +0000 Subject: [PATCH 2/7] Update get-started/develop-in-lightdash/how-to-create-dimensions.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> --- get-started/develop-in-lightdash/how-to-create-dimensions.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/get-started/develop-in-lightdash/how-to-create-dimensions.mdx b/get-started/develop-in-lightdash/how-to-create-dimensions.mdx index affffd56..8cbf6b9c 100644 --- a/get-started/develop-in-lightdash/how-to-create-dimensions.mdx +++ b/get-started/develop-in-lightdash/how-to-create-dimensions.mdx @@ -88,7 +88,7 @@ For example, if I had a column in my dbt model called `source` and I wanted to a ... ``` - + ```yaml models: - name: Pages @@ -152,7 +152,7 @@ You can jazz up your dimensions by configuring them in your .yml files. These di ...etc ``` - + ```yaml models: - name: orders From d2676568f7cccb7b403d1db5f7994bd97c8cb467 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Thu, 12 Feb 2026 19:50:06 +0000 Subject: [PATCH 3/7] Update references/tables.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> --- references/tables.mdx | 38 +++++++++++++++++++------------------- 1 file changed, 19 insertions(+), 19 deletions(-) diff --git a/references/tables.mdx b/references/tables.mdx index 945a79c5..94f93209 100644 --- a/references/tables.mdx +++ b/references/tables.mdx @@ -61,7 +61,7 @@ You can customize how Tables look in Lightdash by adding configuration to your Y relationship: one-to-one ``` - + ```yaml models: - name: users @@ -176,7 +176,7 @@ By default, the fields in your sidebar for any table will appear alphabetically - name: user_email ``` - + ```yaml models: - name: users @@ -250,7 +250,7 @@ For example, you might use this if you want your Lightdash explore to query from sql_from: my_schema.my_sales_view ``` - + ```yaml models: - name: sales @@ -284,7 +284,7 @@ For example: sql_filter: ${TABLE}.sales_region = 'EMEA' ``` - + ```yaml models: - name: sales @@ -326,7 +326,7 @@ For example: sql_filter: ${TABLE}.sales_region IN (${lightdash.attributes.sales_region}) ``` - + ```yaml models: - name: sales @@ -378,7 +378,7 @@ In the example below, only users with `is_admin` attribute `true` can use the `p is_admin: "true" ``` - + ```yaml models: - name: payments @@ -421,7 +421,7 @@ If your table has a single column that uniquely identifies each row, you can def primary_key: user_id ``` - + ```yaml models: - name: users @@ -453,7 +453,7 @@ If your table requires multiple columns to uniquely identify each row, you can d primary_key: [order_id, item_id] ``` - + ```yaml models: - name: order_items @@ -502,7 +502,7 @@ Individual metrics can override the model-level default by specifying their own - custom_field # Overrides the model default ``` - + ```yaml models: - name: payments @@ -575,7 +575,7 @@ Below you can see there is a default filter with the optional required flag, tha type: date ``` - + ```yaml models: - name: orders @@ -637,7 +637,7 @@ Below you can see there is a default filter with the optional required flag, tha type: string ``` - + ```yaml - name: orders config: @@ -700,7 +700,7 @@ Note that we do also support a _legacy_ structure for defining required filters, type: date ``` - + ```yaml models: - name: orders @@ -825,7 +825,7 @@ Available intervals: `milliseconds`, `seconds`, `minutes`, `hours`, `days`, `wee - customer_email: '!%@test.com%' ``` - + ```yaml models: - name: orders @@ -899,7 +899,7 @@ The `parameters` section allows you to define model-level parameters that can be dimension: "department" ``` - + ```yaml models: - name: orders @@ -1019,7 +1019,7 @@ You can also reference model-level parameters from joined tables. This is partic AND ${customers.status} = ${ld.parameters.customers.customer_status} ``` - + ```yaml models: - name: orders @@ -1087,7 +1087,7 @@ Below is an advanced example of using Explores. This will result in three total fields: [industry, segment, unique_accounts, unique_smb_accounts, unique_midmarket_accounts, unique_enterprise_accounts] ``` - + ```yaml models: - name: deals @@ -1191,7 +1191,7 @@ The expand operator (ex. `my_set*`) tells Lightdash to look up the set being ref - my_user_fields* # Reference to the set we defined ``` - + ```yaml models: - name: orders_model @@ -1263,7 +1263,7 @@ In the instance where you want to leverage some, but not all fields in a `set`, - -user_id # Expand `my_user_fields` and exclude `user_id` ``` - + ```yaml models: - name: orders_model @@ -1339,7 +1339,7 @@ Within a model, you may join with other model tables. The sets you define can re - revenue_fields* ``` - + ```yaml models: - name: purchases From c54b6d68082d406b1794320ae23da12bc49169b3 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Thu, 12 Feb 2026 19:50:09 +0000 Subject: [PATCH 4/7] Update references/metrics.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> --- references/metrics.mdx | 48 +++++++++++++++++++++--------------------- 1 file changed, 24 insertions(+), 24 deletions(-) diff --git a/references/metrics.mdx b/references/metrics.mdx index e735ea87..11b034d1 100644 --- a/references/metrics.mdx +++ b/references/metrics.mdx @@ -31,7 +31,7 @@ To add a metric to Lightdash using the `meta` tag, you define it in your dbt pro type: sum # metric type ``` - + ```yaml models: - name: orders_model @@ -91,7 +91,7 @@ Sometimes a metric references multiple columns, in these cases you can define th sql: ${revenue} + ${taxes_paid} ``` - + ```yaml models: - name: orders_model @@ -201,7 +201,7 @@ You can customize your metrics in your dbt model's YAML file. Here's an example - is_adjusted: true ``` - + ```yaml models: - name: sales_stats @@ -335,7 +335,7 @@ For example, this creates a metric `median_price` by taking the 50% percentile o percentile: 50 ``` - + ```yaml columns: - name: item_price @@ -383,7 +383,7 @@ For example, this creates a metric `median_price` by taking the 50% percentile o type: median ``` - + ```yaml columns: - name: item_price @@ -429,7 +429,7 @@ For example, this creates a metric `avg_price` by taking the average of the `ite type: average ``` - + ```yaml columns: - name: item_price @@ -480,7 +480,7 @@ For example, the `avg_price` metric below is an average of all of the `item_pric sql: 'IF(${avg_price} > 20, TRUE, FALSE)' ``` - + ```yaml columns: - name: item_price @@ -532,7 +532,7 @@ For example, this creates a metric `number_of_users` by counting the number of ` type: count ``` - + ```yaml columns: - name: user_id @@ -578,7 +578,7 @@ For example, this creates a metric `number_of_unique_users` by counting the numb type: count_distinct ``` - + ```yaml columns: - name: user_id @@ -629,7 +629,7 @@ If you want to create a metric of a maximum or minimum date, you can't use `type sql: MAX(${TABLE}.created_at_date) ``` - + ```yaml columns: - name: created_at_date @@ -682,7 +682,7 @@ For example, this creates a metric `max_delivery_cost` by looking at the `delive type: max ``` - + ```yaml columns: - name: delivery_cost @@ -730,7 +730,7 @@ For example, this creates a metric `min_delivery_cost` by looking at the `delive type: min ``` - + ```yaml columns: - name: delivery_cost @@ -784,7 +784,7 @@ For example, this creates a metric called `total_gross_profit_margin_percentage` sql: '(${total_gross_profit_margin}/ NULLIF(${total_sale_price},0))' ``` - + ```yaml columns: - name: sale_price @@ -848,7 +848,7 @@ For example, this creates a metric `total_revenue` by adding up the values in th type: sum ``` - + ```yaml columns: - name: revenue @@ -891,7 +891,7 @@ For example, this creates a metric `total_revenue` by adding up the values in th sql: 'SUM(DISTINCT ${revenue})' ``` - + ```yaml columns: - name: revenue @@ -942,7 +942,7 @@ For example, this creates a metric `product_name_group` by combining the unique sql: 'GROUP_CONCAT(${TABLE}.product_name)' ``` - + ```yaml columns: - name: product_name @@ -991,7 +991,7 @@ For example, to calculate the percent of the previous value of total revenue: format: '0.00%' ``` - + ```yaml models: - name: orders_model @@ -1049,7 +1049,7 @@ For example, to calculate each row's percent of total revenue: format: '0.00%' ``` - + ```yaml models: - name: orders_model @@ -1105,7 +1105,7 @@ For example, to calculate a running total of revenue: sql: ${total_revenue} ``` - + ```yaml models: - name: orders_model @@ -1434,7 +1434,7 @@ To do this, you need to set up `group_details` in the model's configuration. The groups: ['product_details'] # this would add the metric under the group label: `product_details` ``` - + ```yaml models: - name: baskets @@ -1531,7 +1531,7 @@ For example, we could add a filter to our users count to make sure it didn't inc - is_closed_account: false ``` - + ```yaml models: - name: sales_stats @@ -1636,7 +1636,7 @@ To filter a field using a list of values you can supply them as an array for tha - shipped ``` - + ```yaml columns: - name: order_id @@ -1712,7 +1712,7 @@ To filter using a field from a joined model, just use the syntax `model_name.fie - web_sessions.is_bot_user: false ``` - + ```yaml models: - name: sales_stats @@ -1818,7 +1818,7 @@ Here's an example: imagine you wanted to calculate the average cost per item tha - status: 'shipped' ``` - + ```yaml models: - name: orders From c1d6f9db52ec3f1fada6b585873b3b10d48858e1 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Thu, 12 Feb 2026 19:50:16 +0000 Subject: [PATCH 5/7] Update references/dimensions.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> --- references/dimensions.mdx | 54 +++++++++++++++++++-------------------- 1 file changed, 27 insertions(+), 27 deletions(-) diff --git a/references/dimensions.mdx b/references/dimensions.mdx index b4b2e968..36572850 100644 --- a/references/dimensions.mdx +++ b/references/dimensions.mdx @@ -67,7 +67,7 @@ If you want to declare multiple dimensions based on the same column, check [addi is_admin: 'true' ``` - + ```yaml models: - name: sales_stats @@ -179,7 +179,7 @@ The types of your dimensions are pulled from your data warehouse, automatically. type: date ``` - + ```yaml - name: user_created_date config: @@ -292,7 +292,7 @@ To help you build your format expression, we recommend using https://customforma format: '0.00%' # 0.67895243 will appear as '67.89% ``` - + ```yaml - name: us_revenue config: @@ -374,7 +374,7 @@ To help you build your format expression, we recommend using https://customforma format: 'gbp' ``` - + ```yaml models: - name: sales_stats @@ -429,7 +429,7 @@ To help you build your format expression, we recommend using https://customforma round: 0 # equivalent format expression: '#,##0.0' ``` - + ```yaml models: - name: sales @@ -470,7 +470,7 @@ You can compact values in your YAML. For example, if I wanted all of my revenue compact: thousands # You can also use 'K' ``` - + ```yaml models: - name: sales @@ -568,7 +568,7 @@ In this example, `created` would now appear as a single, timestamp dimension wit time_intervals: OFF ``` - + ```yaml - name: created description: 'Timestamp when the user was created.' @@ -609,7 +609,7 @@ If you specify time intervals manually, then this overrides the default time int time_intervals: ['DAY', 'DAY_OF_MONTH_NUM', 'MONTH', 'QUARTER_NAME', 'YEAR'] ``` - + ```yaml - name: created description: 'Timestamp when the user was created.' @@ -695,7 +695,7 @@ You can set custom versions of time intervals by using additional dimensions and groups: ["Delivery Date"] ``` - + ```yaml - name: delivery_date config: @@ -799,7 +799,7 @@ To do this, you need to set up `group_details` in the model's configuration. The groups: ['product_details'] # this would add the dimension under the group label: `product_details` ``` - + ```yaml models: - name: baskets @@ -878,7 +878,7 @@ Lightdash users can interact with dimension values by clicking on them. If you'r url: ${ value.raw } ``` - + ```yaml columns: - name: candidate_profile_url @@ -929,7 +929,7 @@ In the example below, users can click on a company name and open a corresponding url: 'https://mycrm.com/companies/${ row.company.company_id.raw | url_encode }' ``` - + ```yaml columns: - name: company_name @@ -978,7 +978,7 @@ You can reference another dimension from your table in your URL. For these URLs url: "https://example.com/company/${row.customers.customer_id.raw | url_encode }" ``` - + ```yaml columns: - name: company_name @@ -1064,7 +1064,7 @@ In the example below, only users with `is_admin` attribute `true` can use the `s is_admin: "true" ``` - + ```yaml columns: - name: @@ -1125,7 +1125,7 @@ You can predefine colors for your string type dimensions, these colors will be u "returned": "#E91E63" ``` - + ```yaml - name: status description: "{{ doc(\"orders_status\") }}" @@ -1200,7 +1200,7 @@ If your column already contains complete image URLs, you can simply configure it url: "${value.raw}" ``` - + ```yaml columns: - name: image_url @@ -1245,7 +1245,7 @@ You can control the size and display behavior of images using width, height, and fit: "cover" ``` - + ```yaml columns: - name: product_image_url @@ -1293,7 +1293,7 @@ You can control the size and display behavior of images using width, height, and url: "https://example.com/images/${value.raw}.jpg" ``` - + ```yaml columns: - name: product_id @@ -1339,7 +1339,7 @@ You can control the size and display behavior of images using width, height, and url: "https://cdn.example.com/${value.raw}-${row.events.event_id.raw | upcase}.png" ``` - + ```yaml columns: - name: event_type @@ -1494,7 +1494,7 @@ image: fit: "cover" ``` - + ```yaml models: - name: products @@ -1605,7 +1605,7 @@ To fix this, we can add the quoted column to our `sql` meta tag on dimensions sql: '"orders"."Status"' # you can also use '${TABLE}."Status"' ``` - + ```yaml - name: status config: @@ -1666,7 +1666,7 @@ All [dimension configurations](#dimension-configuration) are available for addit format: '#,##0,," M"' ``` - + ```yaml columns: - name: revenue @@ -1724,7 +1724,7 @@ When defining additional dimensions, you can reference other dimensions, even fr sql: ${created_date} - ${organizations.first_payment_date} ``` - + ```yaml columns: - name: created_date @@ -1779,7 +1779,7 @@ Usually you'll want to add `hidden:true` for the main JSON dimension since raw J sql: JSON_VALUE(${metadata}, '$.version') # custom SQL applied to get the "version" value inside metadata ``` - + ```yaml columns: - name: metadata # this is a jsonb column with metadata @@ -1831,7 +1831,7 @@ You can use additional dimensions to convert a timestamp into multiple timezones sql: "convert_timezone('UTC', 'America/New_York', ${TABLE}.created_at)" ``` - + ```yaml columns: - name: created_at @@ -1900,7 +1900,7 @@ To define metrics based on additional dimensions, you need to add them to the mo sql: ${version} ``` - + ```yaml models: - name: users @@ -1983,7 +1983,7 @@ For example, you can create a tier based on whether a specific time interval has ELSE 'else' END ``` - + ```yaml - name: session_start config: From 69e1e2e180a54fc968de3ab789c6ccbe37147c17 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Thu, 12 Feb 2026 19:50:17 +0000 Subject: [PATCH 6/7] Update references/joins.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> --- references/joins.mdx | 38 +++++++++++++++++++------------------- 1 file changed, 19 insertions(+), 19 deletions(-) diff --git a/references/joins.mdx b/references/joins.mdx index 2de5817d..1c376186 100644 --- a/references/joins.mdx +++ b/references/joins.mdx @@ -27,7 +27,7 @@ Joins are defined at the same level as the model parameters in your YAML file. relationship: one-to-many ``` - + ```yaml models: - name: accounts @@ -87,7 +87,7 @@ When joining tables, you may want to rename for readability. This can be done wi sql_on: ${messages.sent_by} = ${users.user_id} ``` - + ```yaml models: - name: messages @@ -127,7 +127,7 @@ You can also override the description of the joined table by providing a `descri sql_on: ${messages.sent_by} = ${users.user_id} ``` - + ```yaml models: - name: messages @@ -173,7 +173,7 @@ If you need to join a table multiple times, you can use an `alias` to distinguis sql_on: ${messages.sent_to} = ${recipient.user_id} ``` - + ```yaml models: - name: messages @@ -230,7 +230,7 @@ Here's an example of how to specify a join type: sql_on: ${messages.sent_by} = ${users.user_id} ``` - + ```yaml models: - name: messages @@ -286,7 +286,7 @@ Here's an example of how to specify an inner join: type: inner ``` - + ```yaml models: - name: users @@ -329,7 +329,7 @@ Here's an example of how to specify a left join: type: left # you can omit this, as left is the default ``` - + ```yaml models: - name: users @@ -372,7 +372,7 @@ Here's an example of how to specify a right join: type: right ``` - + ```yaml models: - name: users @@ -420,7 +420,7 @@ To define a relationship, add the `relationship` field to your join configuratio relationship: one-to-many ``` - + ```yaml models: - name: users @@ -499,7 +499,7 @@ To define a relationship, add the `relationship` field to your join configuratio type: left ``` - + ```yaml models: - name: accounts @@ -564,7 +564,7 @@ To define a relationship, add the `relationship` field to your join configuratio type: right ``` - + ```yaml models: - name: tracks @@ -656,7 +656,7 @@ To define a relationship, add the `relationship` field to your join configuratio type: left ``` - + ```yaml models: - name: accounts @@ -731,7 +731,7 @@ If you need a table to always be joined, you can set the `always` field to `true always: true ``` - + ```yaml models: - name: messages @@ -774,7 +774,7 @@ Use the `fields` tag to select a subset of fields from a join. This is useful if fields: [user_id, email, name] ``` - + ```yaml models: - name: messages @@ -827,7 +827,7 @@ For example, I can filter one of my metrics using a dimension from my joined mod - subscriptions.plan: premium ``` - + ```yaml models: - name: users @@ -899,7 +899,7 @@ You can also reference joined metrics and dimensions in custom sql, like this: sql: IF(${subscriptions.plan} = 'premium', ${user_id}, NULL) ``` - + ```yaml models: - name: users @@ -978,7 +978,7 @@ Sometimes, you need to use an intermediate model to join two models together and sql_on: organizations.organization_id = map_users_organizations.organization_id ``` - + ```yaml models: - name: users @@ -1221,7 +1221,7 @@ Lightdash can automatically handle deduplicating metrics that are inflated due t relationship: one-to-many ``` - + ```yaml models: - name: users @@ -1443,7 +1443,7 @@ There are a few situations where Lightdash doesn't currently handle inflated met description: 'Pre-aggregated total amount per order. Cannot be meaningfully split by payment method or other transaction-level dimensions.' ``` - + ```yaml models: - name: orders From 62598a7784615c3f785783eb302d655c17b4ab6a Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Thu, 12 Feb 2026 19:50:24 +0000 Subject: [PATCH 7/7] Update guides/metrics-catalog.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> --- guides/metrics-catalog.mdx | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/guides/metrics-catalog.mdx b/guides/metrics-catalog.mdx index 32987f8c..291dacd0 100644 --- a/guides/metrics-catalog.mdx +++ b/guides/metrics-catalog.mdx @@ -138,7 +138,7 @@ This will set the default visibility of metrics in the catalog to `show` for all visibility: hide ``` - + ```yml models: - name: events @@ -178,7 +178,7 @@ This will hide the events model from the catalog. visibility: show ``` - + ```yml models: - name: events @@ -268,7 +268,7 @@ spotlight: - revenue ``` - + ```yml models: - name: events @@ -331,7 +331,7 @@ Now you can add the `marketing` category to the `event_count` metric: - marketing ``` - + ```yml models: - name: events @@ -400,7 +400,7 @@ You can assign owners to metrics using the `spotlight.owner` property. The owner owner: alice@yourcompany.com ``` - + ```yaml models: - name: orders @@ -458,7 +458,7 @@ You can set a default owner for all metrics in a model. Metric-level owners over # inherits bob@yourcompany.com from model ``` - + ```yaml models: - name: orders @@ -534,7 +534,7 @@ Use boolean values at the dimension level to hide a dimension from filter or seg segment_by: false # hide from segment-by dropdown ``` - + ```yaml models: - name: orders @@ -587,7 +587,7 @@ Use an array of dimension names at the metric level to create an allowlist of di - customer_segment ``` - + ```yaml models: - name: orders @@ -678,7 +678,7 @@ To pre-select a time field in the explore view, simply define the default settin type: count ``` - + ```yml models: - name: events @@ -742,7 +742,7 @@ To pre-select a time field in the explore view, simply define the default settin # ... your column definitions here ``` - + ```yaml models: - name: events @@ -806,7 +806,7 @@ This will override the time dimension defined on the table level. interval: MONTH ``` - + ```yaml models: - name: events