From f20b5dbb1f06d20821bca3f00c501e20d2997ce2 Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Fri, 7 Nov 2025 14:46:36 -0500 Subject: [PATCH 1/3] Updating SL Snowflake QS --- website/docs/guides/sl-snowflake-qs.md | 44 ++++---------------------- 1 file changed, 7 insertions(+), 37 deletions(-) diff --git a/website/docs/guides/sl-snowflake-qs.md b/website/docs/guides/sl-snowflake-qs.md index 0fa975acf51..464bcab69b5 100644 --- a/website/docs/guides/sl-snowflake-qs.md +++ b/website/docs/guides/sl-snowflake-qs.md @@ -449,37 +449,9 @@ packages: -7. In the `models` directory, create the file `metrics/metricflow_time_spine.sql` in your main directory. -8. Copy the following query into the file and click **Save**. +7. Create a MetricFlow time spine model following the [MetricFlow time spine guide](/guides/mf-time-spine?step=1). This replaces the old dbt_utils approach and avoids deprecation warnings. - - -```sql -{{ - config( - materialized = 'table', - ) -}} -with days as ( - {{ - dbt_utils.date_spine( - 'day', - "to_date('01/01/2000','mm/dd/yyyy')", - "to_date('01/01/2027','mm/dd/yyyy')" - ) - }} -), -final as ( - select cast(date_day as date) as date_day - from days -) -select * from final - -``` - - - -9. Enter `dbt run` in the command prompt at the bottom of the screen. You should get a successful run message and also see in the run details that dbt has successfully built five models. +8. Enter `dbt run` in the command prompt at the bottom of the screen. You should get a successful run message and also see in the run details that dbt has successfully built your models. ## Create semantic models @@ -642,10 +614,7 @@ semantic_models: To ensure accurate time-based aggregations, you must configure a [time spine](/docs/build/metricflow-time-spine). The time spine allows you to have accurate metric calculations over different time granularities. -1. Add a time spine model to your project at whichever granularity needed for your metrics (like daily or hourly). -2. Configure each time spine in a YAML file to define how MetricFlow recognizes and uses its columns. Follow the instructions in [Configuring time spine in YAML](/docs/build/metricflow-time-spine#configuring-time-spine-in-yaml) documenation. - -For a step-by-step guide, refer to [MetricFlow time spine guide](/guides/mf-time-spine?step=1). +Follow the [MetricFlow time spine guide](/guides/mf-time-spine?step=1) for complete step-by-step instructions on creating and configuring your time spine model. This guide provides the current best practices and avoids deprecated configurations. ## Define metrics and add a second semantic model @@ -658,7 +627,7 @@ In this section, you will [define metrics](#define-metrics) and [add a second se There are different types of metrics you can configure: - [Conversion metrics](/docs/build/conversion) — Track when a base event and a subsequent conversion event occur for an entity within a set time period. -- [Cumulative metrics](/docs/build/metrics-overview#cumulative-metrics) — Aggregate a measure over a given window. If no window is specified, the window will accumulate the measure over all of the recorded time period. Note that you must create the time spine model before you add cumulative metrics. +- [Cumulative metrics](/docs/build/cumulative) — Aggregate a measure over a given window. If no window is specified, the window will accumulate the measure over all of the recorded time period. Note that you must create the time spine model before you add cumulative metrics. - [Derived metrics](/docs/build/metrics-overview#derived-metrics) — Allows you to do calculations on top of metrics. - [Simple metrics](/docs/build/metrics-overview#simple-metrics) — Directly reference a single measure without any additional measures involved. - [Ratio metrics](/docs/build/metrics-overview#ratio-metrics) — Involve a numerator metric and a denominator metric. A constraint string can be applied to both the numerator and denominator or separately to the numerator or denominator. @@ -755,7 +724,8 @@ metrics: type_params: measure: name: order_total - grain_to_date: month + cumulative_type_params: + grain_to_date: month # Derived metric - name: "pct_of_orders_that_are_large" label: "pct_of_orders_that_are_large" @@ -999,7 +969,7 @@ This section will guide you on how to use the Sigma integration to query your me ```sql select * from {{ semantic_layer.query ( - metrics = ['order_total', 'order_count', 'large_orders', 'customers_with_orders', 'avg_order_value', pct_of_orders_that_are_large'], + metrics = ['order_total', 'order_count', 'large_orders', 'customers_with_orders', 'avg_order_value', 'pct_of_orders_that_are_large'], group_by = [Dimension('metric_time').grain('day') ] ) }} From be3e4ff466abc25e725d0630e49a223574ac5a3d Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Fri, 7 Nov 2025 14:49:49 -0500 Subject: [PATCH 2/3] Update website/docs/guides/sl-snowflake-qs.md --- website/docs/guides/sl-snowflake-qs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/guides/sl-snowflake-qs.md b/website/docs/guides/sl-snowflake-qs.md index 464bcab69b5..545beddf825 100644 --- a/website/docs/guides/sl-snowflake-qs.md +++ b/website/docs/guides/sl-snowflake-qs.md @@ -449,7 +449,7 @@ packages: -7. Create a MetricFlow time spine model following the [MetricFlow time spine guide](/guides/mf-time-spine?step=1). This replaces the old dbt_utils approach and avoids deprecation warnings. +7. Create a MetricFlow time spine model following the [MetricFlow time spine guide](/guides/mf-time-spine?step=1). If you've got an existing time spine in your project configured before v1.9, this method replaces the old `dbt_utils` approach, avoids deprecation warnings when using v1.10+, and is required for upgrading to the . 8. Enter `dbt run` in the command prompt at the bottom of the screen. You should get a successful run message and also see in the run details that dbt has successfully built your models. From 48cf8f7e2dabef9e35909dcc96d0d9e3611b3f1d Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Thu, 20 Nov 2025 15:11:36 -0500 Subject: [PATCH 3/3] Update website/docs/guides/sl-snowflake-qs.md Co-authored-by: Leona B. Campbell <3880403+runleonarun@users.noreply.github.com> --- website/docs/guides/sl-snowflake-qs.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/website/docs/guides/sl-snowflake-qs.md b/website/docs/guides/sl-snowflake-qs.md index 545beddf825..2cda08ac060 100644 --- a/website/docs/guides/sl-snowflake-qs.md +++ b/website/docs/guides/sl-snowflake-qs.md @@ -449,7 +449,9 @@ packages: -7. Create a MetricFlow time spine model following the [MetricFlow time spine guide](/guides/mf-time-spine?step=1). If you've got an existing time spine in your project configured before v1.9, this method replaces the old `dbt_utils` approach, avoids deprecation warnings when using v1.10+, and is required for upgrading to the . +7. Create a MetricFlow time spine model following the [MetricFlow time spine guide](/guides/mf-time-spine?step=1). + + **Note:** If your project already uses a time spine configured before v1.9, you can use this method to replace the old `dbt_utils` approach. This new method avoids deprecation warnings in v1.10+ and is required for upgrading to the Engine. 8. Enter `dbt run` in the command prompt at the bottom of the screen. You should get a successful run message and also see in the run details that dbt has successfully built your models.