From 1a7d0d5930b1217ae06da9a9e5ed6814842a9a1f Mon Sep 17 00:00:00 2001 From: ciansnowplow <148253350+ciansnowplow@users.noreply.github.com> Date: Wed, 21 Aug 2024 16:12:33 +0100 Subject: [PATCH] Update yml vars for running in same project I have added the snowplow__user_mapping_source: "{{ ref('snowplow_unified_user_mapping') }}" to the yml vars for running the attribution in the same project as unified. This is required for the model to run successfully. I have also updated a broken link to the unified package. --- .../dbt-quickstart/attribution/index.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/modeling-your-data/modeling-your-data-with-dbt/dbt-quickstart/attribution/index.md b/docs/modeling-your-data/modeling-your-data-with-dbt/dbt-quickstart/attribution/index.md index fa6387b2e9..b064cefbfc 100644 --- a/docs/modeling-your-data/modeling-your-data-with-dbt/dbt-quickstart/attribution/index.md +++ b/docs/modeling-your-data/modeling-your-data-with-dbt/dbt-quickstart/attribution/index.md @@ -96,11 +96,12 @@ Your channel and spend data will be summed separately in the `attribution_overvi
Running both Unified and Attribution dbt packages from the same project -Although auto-deployed packages managed via Console run in separate projects, for others there may be use cases when it is more practical to run both the [Unified Digital](/docs/modeling-your-data/modeling-your-data-with-dbt/dbt-models/dbt-unified-data-model/index.md) and Attribution dbt packages from the same project. We purposefully did not directly link the two packages and this method of running is non-standard but there is a way to make it work. When specifying the sources just make sure you change the default source references to: ref('') instead of hard coding the schema.table_name for these variables: +Although auto-deployed packages managed via Console run in separate projects, for others there may be use cases when it is more practical to run both the [Unified Digital](/docs/modeling-your-data/modeling-your-data-with-dbt/dbt-models/dbt-unified-data-model/) and Attribution dbt packages from the same project. We purposefully did not directly link the two packages and this method of running is non-standard but there is a way to make it work. When specifying the sources just make sure you change the default source references to: ref('') instead of hard coding the schema.table_name for these variables: ```yml snowplow__conversion_path_source: "{{ ref('snowplow_unified_views') }}" snowplow__conversions_source: "{{ ref('snowplow_unified_conversions') }}" +snowplow__user_mapping_source: "{{ ref('snowplow_unified_user_mapping') }}" ``` Keep in mind that the manifest tables are still not linked, therefore both projects' statefulness is dictated by their own set of tables and values.