From 124e4b3faa3e1737f03456c89942295e9bfc2b03 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Fri, 31 May 2024 16:13:40 +0100 Subject: [PATCH] Update exports.md remove multi tenant as exports supports both mt and st. --- website/docs/docs/use-dbt-semantic-layer/exports.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/use-dbt-semantic-layer/exports.md b/website/docs/docs/use-dbt-semantic-layer/exports.md index 2707c2fe585..8f236e3eacc 100644 --- a/website/docs/docs/use-dbt-semantic-layer/exports.md +++ b/website/docs/docs/use-dbt-semantic-layer/exports.md @@ -13,7 +13,7 @@ Essentially, exports are like any other table in your data platform — they ## Prerequisites -- You have a [multi-tenant](/docs/cloud/about-cloud/tenancy) dbt Cloud account on a [Team or Enterprise](https://www.getdbt.com/pricing/) plan. +- You have a dbt Cloud account on a [Team or Enterprise](https://www.getdbt.com/pricing/) plan. - You use one of the following data platforms: Snowflake, BigQuery, Databricks, or Redshift. - You are on [dbt version](/docs/dbt-versions/upgrade-dbt-version-in-cloud) 1.7 or newer. - You have the dbt Semantic Layer [configured](/docs/use-dbt-semantic-layer/setup-sl) in your dbt project.