The easy-to-use open source Business Intelligence and Embedded Analytics tool that lets everyone work with data :bar_chart:
TypeScript analyticsbibusiness-intelligencebusinessintelligenceclojuredashboarddatadata-analysisdata-visualizationdatabasemetabasemysqlpostgrespostgresqlreportingslacksql-editorvisualization
docs - transform indexes (#83598)
Jeff Bruemmerb9b5c25e7a67
diff --git a/docs/ai/agent-driven-development.md b/docs/ai/agent-driven-development.mdindex 3bdc2026286..229cabc29ad 100644--- a/docs/ai/agent-driven-development.md+++ b/docs/ai/agent-driven-development.md@@ -113,9 +113,7 @@ Set up Remote Sync in your production Metabase in Read-only mode pointed at the### 2. Create a branch from the Metabase UI-Switch branches in Metabase, as the Metabase UI is the source of truth for which branch the development instance pushes to and pulls from.--In your development Metabase, click the **branch dropdown** at the top and [create a new branch](../installation-and-operation/remote-sync.md#creating-a-branch) for your work, like `feature/support-dashboard`.+In your development Metabase, [create a new branch](../installation-and-operation/remote-sync.md#creating-a-branch) for your work, like `feature/support-dashboard`. Metabase switches to the new branch. Your local Git checkout doesn't change which branch Metabase pushes to and pulls from.### 3. Ask the agent to create contentdiff --git a/docs/ai/settings.md b/docs/ai/settings.mdindex 79359f5e09c..e5fb0750f3c 100644--- a/docs/ai/settings.md+++ b/docs/ai/settings.md@@ -122,7 +122,7 @@ _Admin > AI_-The **Metabot settings** card has two tabs — **Internal** and **Embedded** — so you can configure Metabot for your internal Metabase separately from [embedded](../embedding/introduction.md) Metabase contexts. That way you can, for example, use Metabot in your Metabase while not granting access to Metabot in your embedded Metabase. Each tab has its own enable toggle, verified-content setting, allowed collection, and prompt suggestions, all configured independently.+The **Metabot settings** card has two tabs, **Internal** and **Embedded**, so you can configure Metabot in different contexts. Each tab has its own enable toggle, verified or curated content setting, allowed collection, and prompt suggestions.### Enable Metabot@@ -143,13 +143,13 @@ The **Enable Embedded Metabot** toggle turns embedded Metabot on or off. The tog- [Full-app embedding](../embedding/full-app-embedding.md): The Metabot icon and keyboard shortcuts are only available when Metabot is enabled. Turning off Embedded Metabot will hide these icons and disable the keyboard shortcuts.- [Modular embedding](../embedding/modular-embedding.md): The toggle doesn't add Metabot anywhere; you have to explicitly include a chat component (like the SDK's [`MetabotQuestion`](../embedding/ai-chat.md)) in your application. If, however, you've added a component, and you turn off the Embedded Metabot toggle, your chat component will stop working, so you should also remove or hide the component in your application.-### Verified content+### Verified or curated content-_Available on both the Internal and Embedded tabs, configured independently._+{% include plans-blockquote.html feature="Verified or curated content" %}-Admins on Pro and Enterprise plans can tell Metabot to only work with [models](../data-modeling/models/models.md) and [metrics](../data-modeling/semantic-layer/metrics.md) that have been [verified](../exploration-and-organization/content-verification.md).+_Available on both the Internal and Embedded tabs, configured independently._-Restricting Metabot to verified models and metrics (and only models and metrics) helps Metabot produce more reliable answers, since you know someone has at least vetted the data Metabot can use.+When turned on, Metabot only uses content that's [verified](../exploration-and-organization/content-verification.md), in an [official collection](../exploration-and-organization/collections.md#official-collections), or published to the [Library](../data-modeling/semantic-layer/library.md). Published tables only count if their [visibility layer](../data-modeling/metadata/managing-tables.md#visibility-layer) is **Final**.### Collection for natural language querying@@ -169,7 +169,7 @@ If you're embedding the Metabot component in an app, you can point embedded MetaPicking **Our analytics** is the same as picking no collection at all, so pick something narrower if you want the scoping to do anything. And once you set a collection, tables drop out of embedded Metabot's search results, so pick a collection with the metrics and models you want people building on.-This setting narrows where embedded Metabot searches; it's _not_ a substitute for setting permissions. Embedded Metabot can still read and query anything the person using it has permissions for. Embedded Metabot can also see the items that person viewed recently, whichever collection those live in. Restricting Metabot to [verified content](#verified-content) narrows those recent items to verified, official, and [Library](../data-modeling/semantic-layer/library.md) content, but it doesn't confine them to the collection you picked. To control what data people can get to in an embed, set [data permissions](../permissions/embedding.md). See also [Set up AI chat in Metabase](../embedding/ai-chat.md#set-up-ai-chat-in-metabase).+This setting narrows where embedded Metabot searches; it's _not_ a substitute for setting permissions. Embedded Metabot can still read and query anything the person using it has permissions for. Embedded Metabot can also see the items that person viewed recently, whichever collection those live in. Restricting Metabot to [verified or curated content](#verified-or-curated-content) narrows those recent items to verified, official, and [Library](../data-modeling/semantic-layer/library.md) content, but it doesn't confine them to the collection you picked. To control what data people can get to in an embed, set [data permissions](../permissions/embedding.md). See also [Set up AI chat in Metabase](../embedding/ai-chat.md#set-up-ai-chat-in-metabase).### Prompt suggestionsdiff --git a/docs/data-modeling/images/create-index.png b/docs/data-modeling/images/create-index.pngnew file mode 100644index 00000000000..ed0d4a51d2dBinary files /dev/null and b/docs/data-modeling/images/create-index.png differdiff --git a/docs/data-modeling/images/index-tab.png b/docs/data-modeling/images/index-tab.pngnew file mode 100644index 00000000000..e421837d72cBinary files /dev/null and b/docs/data-modeling/images/index-tab.png differdiff --git a/docs/data-modeling/images/lookback-window.png b/docs/data-modeling/images/lookback-window.pngnew file mode 100644index 00000000000..2c262f803eeBinary files /dev/null and b/docs/data-modeling/images/lookback-window.png differdiff --git a/docs/data-modeling/images/transform-dependencies.png b/docs/data-modeling/images/transform-dependencies.pngindex 9a7a09aa513..760ebf3e644 100644Binary files a/docs/data-modeling/images/transform-dependencies.png and b/docs/data-modeling/images/transform-dependencies.png differdiff --git a/docs/data-modeling/images/transform-edit-settings.png b/docs/data-modeling/images/transform-edit-settings.pngindex 3dd0816a1d1..27555df7dfe 100644Binary files a/docs/data-modeling/images/transform-edit-settings.png and b/docs/data-modeling/images/transform-edit-settings.png differdiff --git a/docs/data-modeling/images/transform-settings.png b/docs/data-modeling/images/transform-settings.pngdeleted file mode 100644index af60d72c879..00000000000Binary files a/docs/data-modeling/images/transform-settings.png and /dev/null differdiff --git a/docs/data-modeling/images/transforms.png b/docs/data-modeling/images/transforms.pngdeleted file mode 100644index b7d8d4a100f..00000000000Binary files a/docs/data-modeling/images/transforms.png and /dev/null differdiff --git a/docs/data-modeling/images/workspace-mapped-tables.png b/docs/data-modeling/images/workspace-mapped-tables.pngdeleted file mode 100644index 0e6971c983d..00000000000Binary files a/docs/data-modeling/images/workspace-mapped-tables.png and /dev/null differdiff --git a/docs/data-modeling/metadata/managing-tables.md b/docs/data-modeling/metadata/managing-tables.mdindex d3d24018cd1..6036eba3ae7 100644--- a/docs/data-modeling/metadata/managing-tables.md+++ b/docs/data-modeling/metadata/managing-tables.md@@ -11,7 +11,7 @@ redirect_from:_Data Studio > Connected data_-+You can manage table settings and metadata to make it easier for people to work with your data in **Data Studio > Connected data**.diff --git a/docs/data-modeling/semantic-layer/library.md b/docs/data-modeling/semantic-layer/library.mdindex c2ef84a9461..d2a9e399958 100644--- a/docs/data-modeling/semantic-layer/library.md+++ b/docs/data-modeling/semantic-layer/library.md@@ -30,7 +30,7 @@ Once you [create the Library](#create-the-library):- A **Library** section appears in the navigation sidebar of the main app, listing the tables and metrics in your semantic layer.- The data picker in the query builder defaults to showing tables and metrics from the Library to encourage people to use your vetted content.-- If you turn on Metabot's [Verified or curated content](../../ai/settings.md#verified-content) setting, Metabot will only use content that's verified, in an official collection, or published to the Library.+- If you turn on Metabot's [Verified or curated content](../../ai/settings.md#verified-or-curated-content) setting, Metabot will only use content that's verified, in an official collection, or published to the Library.- You can [sync the Library to Git](#versioning-the-library) to version your semantic layer and glossary.### Semantic layerdiff --git a/docs/data-modeling/semantic-layer/metrics.md b/docs/data-modeling/semantic-layer/metrics.mdindex 7a067dff124..66d95b25d2f 100644--- a/docs/data-modeling/semantic-layer/metrics.md+++ b/docs/data-modeling/semantic-layer/metrics.md@@ -55,7 +55,7 @@ To create a metric:You can also create a new metric by going to **Browse > Metrics** in the navigation sidebar and clicking on **+**.- If you're creating a [Library metric](./library.md#metrics), you can also [navigate to the Library](./library.md) and click **+ New > Metric**.+ If you're creating a [Library metric](./library.md#metrics), you can also go to [Data Studio > Semantic layer](./library.md) and click **+ New > Metric**.2. Select your starting data. You can start from a table, saved question, model, or another metric.diff --git a/docs/data-modeling/semantic-layer/published-tables.md b/docs/data-modeling/semantic-layer/published-tables.mdindex fe1d1e09139..5fc7bc90a64 100644--- a/docs/data-modeling/semantic-layer/published-tables.md+++ b/docs/data-modeling/semantic-layer/published-tables.md@@ -11,7 +11,7 @@ _Data Studio > Semantic layer_Published tables are the tables you add to your [semantic layer](library.md#semantic-layer). They live in the **Data** collection.-Published tables also show up in the **Library** section of the main app's navigation sidebar. When people pick data for a new question, Metabase shows published tables first. You can also tell [Metabot](../../ai/metabot.md) to only use [curated content](../../ai/settings.md#verified-content) like published tables, and you can [sync published tables to Git](library.md#versioning-the-library), along with their metadata, segments, and measures.+Published tables also show up in the **Library** section of the main app's navigation sidebar. When people pick data for a new question, Metabase shows published tables first. You can also tell [Metabot](../../ai/metabot.md) to only use [curated content](../../ai/settings.md#verified-or-curated-content) like published tables, and you can [sync published tables to Git](library.md#versioning-the-library), along with their metadata, segments, and measures.We use the word "publish" because the tables in your Library should be finished, polished tables. If your tables need to be cleaned or combined before they're ready for analytical queries, check out [transforms](../transforms/transforms-overview.md).diff --git a/docs/data-modeling/transforms/addons.md b/docs/data-modeling/transforms/addons.mdindex 82a725600ee..c6dd12923a4 100644--- a/docs/data-modeling/transforms/addons.md+++ b/docs/data-modeling/transforms/addons.md@@ -39,11 +39,11 @@ With basic transforms, you can:- **Metabase Cloud**: Basic transform functionality on Metabase Cloud - Starter, Pro, or Enterprise - comes with an additional small fee per successful transform run, see [Pricing](https://www.metabase.com/pricing).- Only people logged in with an email of a [Metabase Store admin](../../cloud/accounts-and-billing.md#add-managers) (not just Metabase _instance_ admins) can [enable basic transforms](./transforms-overview.md#enable-transforms).+ Only admins can [enable basic transforms](./transforms-overview.md#enable-transforms).### Cancel basic transforms-Once basic transforms are enabled on your Metabase Cloud instance, they can't be disabled.+Once basic transforms are enabled on your Metabase Cloud instance, you can't cancel the add-on. To stop paying for runs, an admin can [turn transforms off](./transforms-overview.md#turn-transforms-off).## Advanced transformsdiff --git a/docs/data-modeling/transforms/inspector.md b/docs/data-modeling/transforms/inspector.mdindex 968d5f517c4..3a28941cddf 100644--- a/docs/data-modeling/transforms/inspector.md+++ b/docs/data-modeling/transforms/inspector.md@@ -9,7 +9,7 @@ redirect_from:> Transform inspector requires the [Advanced transforms add-on](addons.md).-_Data Studio > Transforms > [transform name] > Inspect_+_Data Studio > Data transformation > [transform name] > Inspect_The transform inspector gives you a diagnostic view of your transforms. Instead of writing your own SQL to check row counts, join match rates, or column distributions, you can open the **Inspect** tab and let Metabase analyze your transform's inputs and outputs for you. The inspector is especially useful for catching data quality issues (like unmatched rows in joins) before they cause problems downstream.diff --git a/docs/data-modeling/transforms/jobs-and-runs.md b/docs/data-modeling/transforms/jobs-and-runs.mdindex 1618d9b30a9..cb0d9462a36 100644--- a/docs/data-modeling/transforms/jobs-and-runs.md+++ b/docs/data-modeling/transforms/jobs-and-runs.md@@ -7,7 +7,7 @@ redirect_from:# Transform jobs-_Data Studio > Jobs_+_Data Studio > Data transformation > Jobs_Jobs are scheduled runs of transforms based on the transform's tags.@@ -20,7 +20,7 @@ Add tags to transforms so that you can use jobs to run the transforms on a schedTo add a tag to a transform:1. Make sure you have [permissions to edit transforms](./transforms-overview.md#permissions-for-transforms).-2. Visit the transform in **Data studio > Transforms**.+2. Visit the transform in **Data Studio > Data transformation**.3. On the **Settings** page for a transform, add transform tags.By default, Metabase comes with hourly, daily, weekly, and monthly tags and jobs that are run on the corresponding schedules, but you can remove or rename those tags, or create new tags. To create a new tag, just type the new tag's name in **Tags** field (either when viewing a transform or when viewing a job) and select **Create a tag**.@@ -29,8 +29,6 @@ Once you've tagged a transform, you can create a job that uses that tag to run t## Jobs-_Data Studio > Jobs_-Jobs run one or more transforms on schedule based on transform tags.@@ -44,15 +42,11 @@ Jobs will run all transforms tagged with any of the tags, plus any transforms thYou can see which transforms a job will run and in which order on the job's page.-### See all jobs--To see all jobs, go to **Data Studio** and click the **Jobs** at the bottom of the left sidebar.-### Create a jobTo create a new job:-1. Go to **Data Studio > Jobs**+1. Go to **Data Studio > Data transformation > Jobs**2. Click the **+ New** button in the top right.3. Specify the schedule: select one of the built-in schedules or use cron syntax to specify a custom schedule,@@ -62,17 +56,17 @@ To create a new job:### Disable jobs-You can disable jobs without deleting them. Unlike deletion (which is permanent), disabling a job just means it won't run until you re-enable it. This is useful when you want to temporarily stop transforms from running - for example, for debugging purposes. This way you don't your lose configuration settings like tags and schedules.+You can disable a job without deleting it. A disabled job keeps its tags and schedule but won't run until you re-enable it, which is handy when you're debugging.To disable a specific job:-1. Go to **Data studio > Jobs**.+1. Go to **Data Studio > Data transformation > Jobs**.2. Find the job you want to disable and click the **three dots** icon to the right of the job's name.3. Select **Disable**To disable all jobs:-1. Go to **Data studio > Jobs**.+1. Go to **Data Studio > Data transformation > Jobs**.2. Click the **three dots** icon above the table with all the jobs, and select **Disable all**.@@ -81,18 +75,7 @@ Even if you disable all jobs, new jobs will still be created enabled by default.### Re-enable jobs-If you [disabled any jobs](#disable-jobs), you can later re-enable them:--To re-enable a specific job:--1. Go to **Data studio > Jobs**.-2. Find the job you want to re-enable and click the **three dots** icon to the right of the job's name.-3. Select **Re-enable**--To re-enable all jobs:--1. Go to **Data studio > Jobs**.-2. Click the **three dots** icon above the table with all the jobs, and select **Re-enable all**.+To re-enable a job, follow the [steps for disabling jobs](#disable-jobs) and select **Re-enable** (or **Re-enable all**).### Delete a job@@ -102,7 +85,7 @@ Deleted jobs can't be restored. If you want to temporarily stop a job from runniTo delete a job:-1. Go to **Data Studio > Jobs**.+1. Go to **Data Studio > Data transformation > Jobs**.2. Find the job you want to delete and click the **three dots** icon to the right of the job's name.3. Select **Delete**.@@ -121,15 +104,15 @@ Metabase skips a dependency when the dependency:## See which transforms a job will run-The job's page in **Data Studio > Jobs** lists every transform the job will run and in which order. The **Notes** column tells you when Metabase will skip a dependency, and flags dependencies that have no schedule of their own.+The job's page in **Data Studio > Data transformation > Jobs** lists every transform the job will run and in which order. The **Notes** column tells you when Metabase will skip a dependency, and flags dependencies that have no schedule of their own.## Runs-You can see all past and current transform runs (both manual and scheduled) by going to **Data Studio** and clicking on **Runs** at the bottom of the left sidebar. The transform run times will be given in Greenwich Mean Time (GMT).+You can see all past and current transform runs (both manual and scheduled) in **Data Studio > Data transformation > Runs**. Run times are in your Metabase server's timezone (hover the info icon next to **Started at** to see which).-You can click on any transform run to see more details about the run, like the error logs. To go to the transform definition from the transform run page, click on the icon next the transform name in the right sidebar.+You can click on any transform run to see more details about the run, like the error logs. To go to the transform definition from the transform run page, click on the icon next to the transform name in the right sidebar.The "Tags" column in the **Runs** table will only show the transform's specific tags. But the run might not have anything to do with those tags. Another job with different tags could have run the transform because [jobs include all dependent transforms](#jobs-include-all-dependent-transforms).diff --git a/docs/data-modeling/transforms/python-runner.md b/docs/data-modeling/transforms/python-runner.mdindex ecd97c8caa8..27c9d3a3f80 100644--- a/docs/data-modeling/transforms/python-runner.md+++ b/docs/data-modeling/transforms/python-runner.md@@ -200,6 +200,6 @@ Then bring everything up and try a transform:docker compose up -d```-3. You'll need a Pro or Enterprise license with the [Advanced transforms add-on](addons.md). In Metabase, [enable transforms](transforms-overview.md#enable-transforms), then [create a Python transform](python.md#create-a-python-transform) and click **Run**.+3. You'll need a Pro or Enterprise license with the [Advanced transforms add-on](addons.md). In Metabase, [enable transforms](transforms-overview.md#enable-transforms), then [create a Python transform](python.md#create-a-python-transform) and click **Run now** on its **Run** tab.-4. Open **Data Studio > Jobs > Runs** and find your run. If it failed, the run's logs will usually tell you whether Metabase couldn't reach the runner, or the runner couldn't reach MinIO.+4. Open **Data Studio > Data transformation > Runs** and find your run. If it failed, the run's logs will usually tell you whether Metabase couldn't reach the runner, or the runner couldn't reach MinIO.diff --git a/docs/data-modeling/transforms/python.md b/docs/data-modeling/transforms/python.mdindex c782a9ad009..25318ebb5ac 100644--- a/docs/data-modeling/transforms/python.md+++ b/docs/data-modeling/transforms/python.md@@ -37,7 +37,7 @@ To execute Python transforms, you'll need a _Python runner_ - a dedicated enviroOnce you've [set up the Python runner](#set-up-a-python-runner):-1. Go to **Data studio > Transforms**.+1. Go to **Data Studio > Data transformation**.2. Click on **+ New** and select **Python script**.3. Select a database that has the data you want to transform. See [Databases that support transforms](transforms-overview.md#databases-that-support-transforms).@@ -95,7 +95,7 @@ If you have functions or classes you'd like to reuse across multiple transforms,To add things to the common Python library:-1. Go to **Data studio > Transforms**.+1. Go to **Data Studio > Data transformation**.2. Scroll to the very bottom of the transforms list and click on **Python library**.3. Add a Python function or class.@@ -120,10 +120,11 @@ To update a table incrementally, your data has to have a certain structure. SeeTo make a Python transform incremental:-1. Go to the transform's page in **Data studio > Transforms**.+1. Go to the transform's page in **Data Studio > Data transformation**.2. Switch to **Settings** tab.3. In **Field to check for new values**, select the field in one of the source tables that Metabase should scan to determine which records are new or changed. Only some fields are eligible. See [prerequisites for incremental transforms](./transforms-overview.md#prerequisites-for-incremental-transforms).-4. (Optional) To update matching rows instead of appending new ones, [add a merge key](./transforms-overview.md#add-merge-keys-to-upsert-rows).+4. (Optional) To catch late-arriving rows, [set a lookback window](./transforms-overview.md#catch-late-arriving-rows-with-a-lookback-window).+5. (Optional) To update matching rows instead of appending new ones, [add a merge key](./transforms-overview.md#add-merge-keys-to-upsert-rows).## Current limitations of Python transformsdiff --git a/docs/data-modeling/transforms/query.md b/docs/data-modeling/transforms/query.mdindex 757af63b46b..3f75ee039fe 100644--- a/docs/data-modeling/transforms/query.md+++ b/docs/data-modeling/transforms/query.md@@ -28,9 +28,9 @@ For general information about Metabase transforms, see [Transforms](transforms-oOn Metabase Cloud, you need the [**Basic transforms** add-on](addons.md) to create query-based transforms.1. [Enable transforms](transforms-overview.md#enable-transforms).-2. Go to **Data studio > Transforms**.+2. Go to **Data Studio > Data transformation**.-3. Click **+ New** and pick "Query builder", "SQL", or "Copy of existing question".+3. Click **+ New** and pick **Query builder**, **SQL query**, or **Copy of a saved question**.Currently, you can't convert between different transform types (like converting a query builder transform to a SQL-based transform, or a SQL transform into a Python transform). If you want to change your transform built with the query builder into a SQL transform, you'll need to create a new transform with the same target and tags, and delete the old transform.@@ -154,10 +154,11 @@ Once your query has table aliases, you can mark the transform as incremental usiTo make a query transform incremental:-1. Go to the transform's page in **Data studio > Transforms**.+1. Go to the transform's page in **Data Studio > Data transformation**.2. Switch to **Settings** tab.3. In **Field to check for new values**, select the field in one of the source tables that Metabase should scan to determine which records are new or changed. Only some fields are eligible. See [prerequisites for incremental transforms](./transforms-overview.md#prerequisites-for-incremental-transforms).-4. (Optional) To update matching rows instead of appending new ones, [add a merge key](./transforms-overview.md#add-merge-keys-to-upsert-rows).+4. (Optional) To catch late-arriving rows, [set a lookback window](./transforms-overview.md#catch-late-arriving-rows-with-a-lookback-window).+5. (Optional) To update matching rows instead of appending new ones, [add a merge key](./transforms-overview.md#add-merge-keys-to-upsert-rows).## Convert models to transforms@@ -175,7 +176,7 @@ You must be an admin to convert models, and the model's database must [support tTo convert a model into a transform:1. Review [Replacing data sources](../tools/replace-data-sources.md) docs for overview and limitations of the process.-2. Open **Data Studio** and select **Transforms** in the sidebar.+2. Go to **Data Studio > Data transformation**.3. Click **Tools > Migrate models**.4. Find the model you want to convert and click it to open its details panel. The panel shows the model's name, database, and collection, and a list of items that depend on it.5. Click **Convert to a transform**.diff --git a/docs/data-modeling/transforms/transforms-overview.md b/docs/data-modeling/transforms/transforms-overview.mdindex 822c3ab772b..b23dc37e5bc 100644--- a/docs/data-modeling/transforms/transforms-overview.md+++ b/docs/data-modeling/transforms/transforms-overview.md@@ -7,14 +7,12 @@ redirect_from:# Transforms-_Data Studio > Transforms_+_Data Studio > Data transformation_Transforms can be used to, well, transform your data - do stuff like preprocessing, cleaning, joining tables, pre-computing metrics. Transforms give you the ability to do the "T" of "ETL" within Metabase.You'll write a query or a Python script in Metabase, a transform will run this query or script, create a table in your target database containing the results, and sync that table to Metabase, so it can be used as a data source for questions or other transforms.--## Transforms overview- **Transforms** are queries (created either with SQL or the query builder) or Python scripts that write back to your database and create a new, persistent table. Use transforms to clean, join, or pre-aggregate data.@@ -36,9 +34,9 @@ Currently, Metabase can create transforms on the following databases:- Snowflake- SQL Server-You can't create transforms on databases that have [Database routing](../../permissions/database-routing.md) enabled, or on Metabase's Sample Database.+You can't create transforms on databases that have [Database routing](../../permissions/database-routing.md) enabled, or on Metabase's Sample Database (which is SQLite).-Transforms will create tables in your database, so the database user you use for your connection must have appropriate privileges. See [Database users, roles, and privileges](../../databases/users-roles-privileges.md). We suggest using a [Writable connection](../../databases/writable-connection.md) for your database.+Transforms will create tables in your database, so the database user you use for your connection must have [appropriate privileges](../../databases/users-roles-privileges.md). We suggest using a [Writable connection](../../databases/writable-connection.md) for your database.## Types of transforms@@ -56,7 +54,7 @@ Permission configuration for transform depends on your plan.- **Metabase Pro/Enterprise** comes with additional permission controls for transforms: a special [Data Analysts](../../people-and-groups/managing.md) group for non-Admins with potential transform access, and granular transform permissions for each database:- To **see** the list of transforms on your instance, people need to be able to access Data Studio, so they need to be either an Admin or a member of the special [Data Analyst group](../../people-and-groups/managing.md).- - To **execute** transforms on a database, people need to be either Admins on belong to the special [Data Analyst group](../../people-and-groups/managing.md). Additionally people need to have the [Transform permissions](../../permissions/data.md) for that database.+ - To **execute** transforms on a database, people need to be either Admins or belong to the [Data Analyst group](../../people-and-groups/managing.md). Data Analysts also need [Transform permissions](../../permissions/data.md) for that database.## Set up transforms on a self-hosted Metabase@@ -72,32 +70,27 @@ If you run Metabase yourself, here's the path to working transforms:Before you can start writing transforms, you'll need to enable transforms in your Metabase instance.-If you're on a Metabase Cloud plan, only people logged in with an email of a [Metabase Store admin](../../cloud/accounts-and-billing.md#add-managers) (not just Metabase _instance_ admins) can enable basic transforms, because transforms incur a cost per run on Metabase Cloud.+If you're on a Metabase Cloud plan, only admins can enable basic transforms, because transforms incur a cost per run on Metabase Cloud.To enable transforms:-1. Navigate to [**Data Studio**](../data-studio.md) by click the **grid icon** in top right corner of your Metabase and selecing **Data Studio**.-2. In Data Studio, click **Transforms** in the right sidebar.-3. If the transforms have not been enabled on your instance yet, you'll see a prompt to enable them. You can do just that.+1. Navigate to [**Data Studio**](../data-studio.md) by clicking the **grid icon** in the top right corner of your Metabase and selecting **Data Studio**.+2. Click **Data transformation**.+3. Click **Enable transforms**. On Metabase Cloud, you'll then need to agree to the Basic transforms add-on pricing.Once you've enabled transforms, you can [configure permissions](#permissions-for-transforms) and start [creating transforms](#create-a-transform).-## See all transforms--_Data Studio > Transforms_--See [permissions needed to see transforms](#permissions-for-transforms).+### Turn transforms off-You can see all your Metabase's transforms:+_Data Studio > Settings_-1. Click the **grid** icon on top right and go to **Data Studio**.-2. In the left sidebar, select **Transforms**.+Admins can turn transforms off with the **Transforms** toggle. While transforms are off, **Data transformation** disappears from Data Studio and no transforms run, manually or on a schedule. Metabase keeps your transforms, jobs, and tables.-+If you've set [`MB_TRANSFORMS_ENABLED`](../../configuring-metabase/environment-variables.md#mb_transforms_enabled), the environment variable wins: you can still flip the toggle, but it won't do anything.## Create a transform-_Data Studio > Transforms_+_Data Studio > Data transformation_> If you're using remote sync, you won't be able to create transforms if your instance is in ["read-only" sync mode](../../installation-and-operation/remote-sync.md).@@ -107,7 +100,7 @@ To create a transform:1. [Enable transforms](#enable-transforms).2. Click the **grid** icon on top right and go to **Data Studio**.-3. In the left sidebar, select **Transforms**.+3. Click **Data transformation**.4. Click **+ New** and select a source for your transform.@@ -134,13 +127,11 @@ To create a transform:- **Folder** (optional): The folder where the transform should live. Click on the field to pick a different folder or create a new one.- **Incremental transformation** (optional): see [Incremental query-based transforms](query.md#incremental-query-transforms) or [Incremental Python transforms](python.md)- -7. Optionally, once the transform is saved, assign tags to your transform. Tags are used by [jobs](./jobs-and-runs.md) to run transforms on schedule.## Edit a transform-_Data Studio > Transforms_+_Data Studio > Data transformation_You can edit the transform's name and description, query/script, target table, and incremental settings. You can edit the transform even if it already ran or is scheduled to run.@@ -150,13 +141,13 @@ If you're using remote sync, you won't be able to edit transforms if your instan### Edit transform's query or script-_Data Studio > Transforms > Definition_+_Data Studio > Data transformation > [transform name] > Definition_See [permissions to edit transforms](#permissions-for-transforms).To edit the transform's query or script:-1. Go to **Data Studio > Transforms**.+1. Go to **Data Studio > Data transformation**.2. Find the transform you'd like to edit and click on **Edit definition** above the transform definition.3. Edit the query or script.@@ -166,7 +157,7 @@ Once you change the transform's query or script, the next transform run (manual### Edit transform's target-_Data Studio > Transforms > Settings_+_Data Studio > Data transformation > [transform name] > Settings_To edit transform's target table, i.e., the table where the query results are written, go the transforms **Settings** tab and click on **Change target**. You'll need to select whether you want to keep the old target table, or delete it. Deletion can't be undone.@@ -176,7 +167,7 @@ To edit transform's target table, i.e., the table where the query results are wrYou can run a transform manually or schedule the transform using tags and jobs.-- To run a transform manually, visit the transform in **Data Studio > Transforms > Runs** and click **Run**.+- To run a transform manually, open the transform in **Data Studio > Data transformation**, go to its **Run** tab, and click **Run now**.- To schedule a transform, you'll need to assign one or more tags to it, then create a [scheduled job](./jobs-and-runs.md) that picks up those tags.@@ -186,9 +177,31 @@ You can see the time and status of the latest transform run on the transform's pFor Python transforms, you'll also see the transform's execution logs.+## Add indexes to a transform's table++_Data Studio > Data transformation > [transform name] > Indexes_++Indexes can speed up queries on a transform's table. Metabase saves the indexes you add here and recreates indexes whenever the transform rebuilds its table. Indexes created directly in your database show as **Unmanaged**: you can't edit or delete them in Metabase, and they disappear the next time the transform rebuilds its table. To keep an index, add it here.++++To add an index:++1. Run the transform at least once, so its table exists.+2. On the transform's **Indexes** tab, click **Create index**.+3. Pick an index type and the columns to index. Types depend on your database: for example, B-Tree indexes on PostgreSQL, sort keys on Redshift, clustering keys on Snowflake, or clustering on BigQuery.++ ++4. Run the transform (or wait for its next scheduled run).++Index edits and deletions take effect on the next run. On an incremental transform, the next run after _any_ index change _rebuilds the whole table_.++If Metabase can't create an index, the index shows as **Failed** and the run usually fails too. Every run retries the index until it succeeds, or until you edit or delete it. On an incremental transform, each of these runs rebuilds the whole table.+## Inspect a transform-_Data Studio > Transforms > [transform name] > Inspect_+_Data Studio > Data transformation > [transform name] > Inspect_> Transform inspector requires the [Advanced transforms add-on](addons.md)@@ -198,7 +211,7 @@ The [transform inspector](./inspector.md) lets you poke at the input and outputs{% include plans-blockquote.html feature="Transform dependencies" is_plural=true%}-_Data Studio > Transforms > Dependencies_+_Data Studio > Data transformation > [transform name] > Dependencies_@@ -206,13 +219,11 @@ Transform queries can use the data from other transforms, and query-based transfMetabase will track transform dependencies and execute transforms in a reasonable order. So for example, if transform B relies on a table created by transform A, Metabase will run transform A first, then run transform B.-On Metabase Pro or Enterprise plans, you can see the transform dependencies graph by going to **Data Studio > Transforms** and go to the **Dependencies** tab.-If a job includes a transform that depends on a table created by another transform, then the job will run all the tagged transforms, plus any of their [dependencies that aren't already up to date](jobs-and-runs.md#jobs-include-all-dependent-transforms).## Incremental transforms-_Data Studio > Transforms > Settings_+_Data Studio > Data transformation > [transform name] > Settings_Incremental transforms only process the data that's new since the previous transform run. For example, you might have new transaction data coming in every day, and run the transform nightly. With each run, the incremental transform would only handle the rows added after the previous run the night before.@@ -223,7 +234,7 @@ In this case, the checkpoint field decides which rows count as new, and the merg### Prerequisites for incremental transforms- There is a column in your data that Metabase can check for new values to determine which data is new. We'll refer to this as a "Checkpoint" column.-- The checkpoint column has to have increasing values, like a sequential ID or timestamp column. Metabase will determine what "new" data is by looking for values that are _greater than_ already-written checkpoint values.+- The checkpoint column has to have increasing values, like a sequential ID or timestamp column. Metabase will determine what "new" data is by looking for values that are _greater than_ already-written checkpoint values. Columns that only store a time of day can't be checkpoints, since their values start over every day.- Your schema is stable, meaning that the structure of the tables is not going to change from run to run.### Add merge keys to upsert rows@@ -234,7 +245,7 @@ Why you'd want to add a merge key: some source tables get a new row each time aTo add a merge key:-1. Go to the transform's page in **Data studio > Transforms**.+1. Go to the transform's page in **Data Studio > Data transformation**.2. Switch to the **Settings** tab and turn on **Only process new data**.3. In **Merge key**, choose the columns that identify a record. If the target table already exists, you'll pick from a list of its columns. If the transform hasn't run yet, there's no table to pick from, so type each column name and press comma or enter. In that case, type the column's name in the database, which may differ from the display name you'd see in the list.@@ -242,6 +253,22 @@ The merge key refers to columns in the _target_ table (the columns your transforMerge keys need a checkpoint field that increases every time a row is written, like an `updated_at` timestamp, otherwise the transform never sees the change.+### Catch late-arriving rows with a lookback window++If, for example, a row stamped 9:55 is added to a table _after_ a transform run has already processed everything through 10:00, later runs won't pick up the row. To catch late-arriving rows, set a lookback window, so each run also reprocesses some data it's already seen.++To set a lookback window:++1. Go to the transform's **Settings** tab and turn on **Only process new data**.+2. In **Field to check for new values**, pick a date or datetime column, like `updated_at`. The **Lookback window** field only shows up for date or datetime checkpoint columns, not number columns like IDs.+3. In **Lookback window**, enter a number and pick a unit, like 4 hours. Each run then also reprocesses rows from the four hours before the checkpoint. Date-only columns can't use units smaller than days.++ ++If you later switch the checkpoint to a column that doesn't support a lookback, Metabase clears the lookback window. If you switch to a date-only column, Metabase changes a minutes or hours unit to days, so a 4-hour window becomes 4 days.++You should pair a lookback window with a [merge key](#add-merge-keys-to-upsert-rows). Otherwise, every run appends the reprocessed rows again as duplicates.+### Reprocess all data to rebuild the target tableOnce an incremental transform has run, its **Settings** tab shows **Last processed [checkpoint field]**, followed by the highest checkpoint value Metabase has written so far. That value is how Metabase knows where to pick up, since each run only handles rows past it.@@ -256,7 +283,7 @@ Incremental transforms work differently for query-based transforms and Python tr## Versioning transforms-_Admin > General > Remote sync_+_Admin > Settings > Remote sync_{% include plans-blockquote.html feature="Versioning transforms" %}@@ -265,8 +292,8 @@ You can check your transforms into git with [Remote Sync](../../installation-andTo enable git sync of transforms:1. Go to Admin settings by clicking the **grid** icon in top right and select **Admin**.-2. On the **General** tab, pick **Remote sync** in the left sidebar.-3. Follow the steps to [Set up Remote Sync](../../installation-and-operation/remote-sync.md), and toggle "Transforms" sync on.+2. On the **Settings** tab, pick **Remote sync** in the left sidebar.+3. Follow the steps to [Set up Remote Sync](../../installation-and-operation/remote-sync.md), and toggle **Transforms** sync on.Keep in mind that this setting only controls whether transforms are checked _into_ the git repo. The transform sync setting does _not_ affect how the instance behaves in read-only mode. If your instance is in read-only mode, you will not be able to create or edit transforms.diff --git a/docs/exploration-and-organization/history.md b/docs/exploration-and-organization/history.mdindex cb6b593cf6b..84424b329f4 100644--- a/docs/exploration-and-organization/history.md+++ b/docs/exploration-and-organization/history.md@@ -30,7 +30,7 @@ Metabase will keep track of a version each time you save, move, revert, [move to### Viewing tracked changes-1. Go to your transform in [Data studio](../data-modeling/transforms/transforms-overview.md).+1. Go to your transform in [Data Studio > Data transformation](../data-modeling/transforms/transforms-overview.md).2. Click the **three dots** icon and select **History**3. The History tab will display the item's history of up to 15 versions.@@ -38,12 +38,12 @@ Any change to the transform's query or script will be recorded as "changed sourc### Reverting to previous versions-1. Go to your transform in [Data studio > Transforms](../data-modeling/transforms/transforms-overview.md).+1. Go to your transform in [Data Studio > Data transformation](../data-modeling/transforms/transforms-overview.md).2. Click the **three dots** icon and select **History**.3. Click the **back arrow** beside a version to revert your item to that point in time.## History for segments and measures-1. Go to the table source for the segment or measure in [Data Studio > Tables](../data-modeling/metadata/managing-tables.md).+1. Go to the table source for the segment or measure in [Data Studio > Connected data](../data-modeling/metadata/managing-tables.md).2. Pick the segment or measure in the right sidebar.3. On the segment or measure's page, go to **Revision history** tab.diff --git a/docs/installation-and-operation/images/branch-dropdown.png b/docs/installation-and-operation/images/branch-dropdown.pngdeleted file mode 100644index fbcfc9a13bf..00000000000Binary files a/docs/installation-and-operation/images/branch-dropdown.png and /dev/null differdiff --git a/docs/installation-and-operation/images/push-changes.png b/docs/installation-and-operation/images/push-changes.pngdeleted file mode 100644index a59577f9d84..00000000000Binary files a/docs/installation-and-operation/images/push-changes.png and /dev/null differdiff --git a/docs/installation-and-operation/remote-sync.md b/docs/installation-and-operation/remote-sync.mdindex caff4aa16ed..cf8c6514aa2 100644--- a/docs/installation-and-operation/remote-sync.md+++ b/docs/installation-and-operation/remote-sync.md@@ -10,8 +10,7 @@ description: Version control your dashboards, questions, and transforms. Sync yoRemote Sync lets you develop analytics content in your Metabase and automatically deploy it to a read-only production Metabase through Git. Remote Sync can sync:- Top-level collections (dashboards, questions, models, metrics)-- Library content (published tables and their segments and measures)-- Snippets+- Library content (published tables with their segments and measures, plus metrics, snippets, and the glossary)- TransformsMetabase doesn't sync any of your data. All Metabase stores in Git are [YAML files](./serialization.md#example-of-a-serialized-question) that describe your analytics content. Your actual data stays in your databases and never leaves your Metabase.@@ -146,21 +145,21 @@ In the Metabase instance that you use for development:6. (Optional) If you have [multi-tenant user strategy enabled](../embedding/tenants.md#enable-multi-tenant-strategy), you can also choose which [shared collection](../embedding/tenants.md#changing-tenant-strategy) to sync.+> If you only want to sync your Library and transforms, you can set up remote sync from Data Studio instead: click **Set up remote sync** at the bottom of the Data Studio sidebar.+### 4. Select what to syncSelect what you [want to sync](#you-choose-what-to-sync).### 5. Push your changes to your repository--Once you've added content, you'll see a yellow dot on the synced collections indicating uncommitted changes.-1. At the top of the screen, choose which branch to push to and click the up arrow (push) icon.+1. At the top of the screen, click the branch name and select **Push changes**.-2. Enter a commit message describing your changes (e.g., "Added dashboard on mammoth populations").+2. (Optional) Describe your changes (e.g., "Added dashboard on mammoth populations").-3. Click "Push changes" to commit and push your changes to your repository.+3. Click **Push changes** to commit and push your changes to your repository.Check your repository; you should see the collection.@@ -207,8 +206,8 @@ In your production Metabase instance:- Click "Save changes". Metabase will verify it can reach your repository. If the connection fails, verify your token has the appropriate permissions and hasn't expired.6. Sync your content:- - Click "Pull changes" to immediately sync content from your repository.- - To keep your production instance automatically updated, toggle on "Auto-sync with Git". Metabase will pull changes from your main branch every five minutes.+ - Click "Pull changes now" to immediately sync content from your repository.+ - To keep your production instance automatically updated, toggle on "Auto-sync with git". Metabase will pull changes from your main branch every five minutes.In Read-only mode, synced collections appear in the regular collections list with a special icon to indicate that they're versioned and read-only.@@ -275,7 +274,7 @@ Let's say your team wants to build a new analytics dashboard. Here's a workflow### Step 1: Create a new branch-In your development Metabase, click the branch dropdown at the top of the screen to [create a new branch](#branch-management) for your work, like `feature/megafauna-dashboard`.+In your development Metabase, go to **Admin** > **Settings** > **Remote sync** and [create a new branch](#creating-a-branch) for your work, like `feature/megafauna-dashboard`.### Step 2: Create content in your development Metabase@@ -283,10 +282,7 @@ Create a dashboard called "Megafauna Analytics" and add some questions. Save the### Step 3: Push to your development branch-1. You should see a yellow dot on your synced collection (indicating local changes).-2. Click the up arrow (push) icon at the top of the screen.-3. Enter a commit message: "Add Megafauna Analytics dashboard".-4. Metabase commits your changes to the branch you're working on and pushes them to your repo.+[Push your changes](#committing-and-pushing-your-changes) to `feature/megafauna-dashboard` with a commit message like "Add Megafauna Analytics dashboard".### Step 4: Create a pull request@@ -312,14 +308,12 @@ On your production Metabase instance:### Synced collections in the UI-You can select any top-level collection under Our Analytics to sync with Git. Synced collections show their current state with visual indicators: a yellow dot indicates unsynced local changes that need to be committed. At the top of the screen, you'll see up/down arrows that provide sync controls for pulling and pushing changes.+You can select any top-level collection under Our Analytics to sync with Git. Synced collections show their current state with visual indicators: a yellow dot indicates unsynced local changes that need to be committed. At the top of the screen (in Data Studio, at the top of the sidebar), click the branch name to push or pull changes.If you are using [tenants](../embedding/tenants.md), you can also sync shared collections. You'll see the same yellow dot indicator for shared collections.In Read-only mode, synced collections appear in the regular collections list (not in a separate "Synced Collections" section) with a special icon to indicate they're versioned and read-only.-When transforms syncing is enabled, you'll find your transforms in the Transforms section of the Admin settings. Synced transforms are also read-only in Read-only mode.-### Moving and deleting content in synced collectionsWhen you remove content from a synced collection in Read-write mode and push that change, the content will also be removed from your production instance when it syncs. This applies to moving content out of a synced collection or deleting it entirely.@@ -369,7 +363,7 @@ Remote Sync uses the same serialization format as the [Metabase CLI serializatio- Documents- Timelines and events- Collection structure and metadata-- Library content (published tables, metrics, snippets, segments, measures)+- Library content (published tables, metrics, snippets, segments, measures, glossary)- Transforms (including jobs and folders)**What doesn't sync:**@@ -386,44 +380,36 @@ Branching is only available in Read-write mode.### Creating a branch-You can create branches in Metabase or directly in your Git repository. Branches created in Git will appear in the Metabase branch dropdown once Metabase syncs with your repository.+You can create branches in Metabase or directly in your Git repository. Branches created in Git will appear in Metabase once Metabase syncs with your repository.Before creating branches, push an initial commit to your main branch.To create a new branch in Metabase:-1. Click the branch dropdown at the top of the screen.-2. Type a name for the new branch in the search box.-3. Press Enter to create the branch.+1. Go to **Admin** > **Settings** > **Remote sync**.+2. Under **Sync branch**, click the current branch.+3. Type a name for the new branch and click **Create branch "[name]"**.-The new branch is created from your current commit (not the latest commit from the remote).+The new branch is created from your current commit (not the latest commit from the remote), and Metabase switches to it.### Switching branches-At the top of the screen, you'll see a branch dropdown:----1. Click the branch dropdown to see available branches.-2. Select a different branch. This will change the branch for everyone in your Metabase (see [limitations](#branching-limitations)).+1. Go to **Admin** > **Settings** > **Remote sync**.+2. Under **Sync branch**, click the current branch and select a different branch. This will change the branch for everyone in your Metabase (see [limitations](#branching-limitations)).If the branch doesn't appear, ensure it exists in your Git repository and that the name matches exactly (branch names are case-sensitive).-If you have unsynced changes, Metabase will show a dialog asking what you want to do:--- **Push changes to the current branch:** Commits your changes to the current branch before switching.-- **Create a new branch and push changes there:** Saves your work to a new branch, keeping the original branch clean.-- **Discard these changes:** Throws away your uncommitted changes (can't be undone).+If you have unsynced changes, Metabase lists them and asks what to do:-The dialog shows you exactly which items have changed, so you can make an informed decision.+- **Push changes to the current branch, [branch]:** Commits your changes to the current branch. You stay on that branch, so pick the other branch again afterward.+- **Create a new branch and push changes there:** Commits your changes to a new branch and switches you to it.+- **Delete unsynced changes (can't be undone):** Throws away your uncommitted changes and switches you to the branch you picked.-If you switch modes (from Read-write to Read-only or vice versa) with unpushed changes, you'll be prompted to save or discard them. You cannot switch to Read-only mode with uncommitted changes.--If changes don't appear after switching modes: Hard refresh your browser (Cmd/Ctrl + Shift + R).+You can't switch to Read-only mode while you have unpushed changes.### Branching limitations-- **Only admins can manage branches**. Non-admins won't see the branch dropdown at all.+- **Only admins can manage branches**. Non-admins don't see the branch controls.- **The current branch is instance-wide**. This means that everyone on the same Metabase is on the same branch at the same time. You can't have different people working on different branches in a single Metabase.Limiting a Metabase to a single branch at a time means that the typical Git feature-branch workflow is a bit different here: only admins can switch branches, create new branches, or push and pull changes. If you need multiple branches worked on simultaneously, the workaround is to spin up multiple Metabases in Read-write mode, one Metabase per branch.@@ -438,22 +424,19 @@ You can only push changes in a Metabase with Remote Sync set to Read-write mode.When you make changes to items in a synced collection, a yellow dot appears on your synced collection (indicating uncommitted changes). To commit and push your changes:-1. Click the up arrow (push) icon at the top of the screen (make sure you're pushing to the right branch).-2. Enter a descriptive commit message explaining your changes.-3. Click "Continue" to push your changes to Git.+1. At the top of the screen, click the branch name and select **Push changes**.+2. (Optional) Describe your changes.+3. Click **Push changes** to push your changes to Git.-If you see a message that "Remote is ahead of local", that means someone else pushed to the branch from another Metabase in Read-write mode. Pull the latest changes before pushing again.+If the branch has new commits since you last pulled, Metabase asks how to handle them before it pushes yours: merge them with yours (when they don't conflict), push your changes to a new branch, or force push over them.## Pulling changes from GitYou can pull changes when in Read-write or Read-only mode.-In Read-write mode, you can get the latest changes from your Git repository:+In Read-write mode, click the branch name at the top of the screen and select **Pull changes**. Metabase imports the latest content from Git.-1. Click the down arrow (pull) icon at the top of the screen.-2. Review any summary of incoming changes if shown.-3. Confirm the import.-4. Metabase updates your collections with the latest content from Git.+In Read-only mode, go to **Admin** > **Settings** > **Remote sync** and click **Pull changes now**.If changes don't appear after pulling:@@ -461,15 +444,14 @@ If changes don't appear after pulling:- Hard refresh your browser (Cmd/Ctrl + Shift + R).- If you encounter sync errors, review error messages in the sync dialog, manually resolve conflicts in your Git repository, then pull again.-In Read-only mode, go to **Admin** > **Settings** > **Remote sync** and click **Pull changes**.--### Handling unsynced changes+### Handling unsynced changes when you pull-If you have local uncommitted changes when trying to pull or switch branches, Metabase will prompt you with options:+If you have local uncommitted changes when you pull, Metabase lists them and asks what to do:-- **Push changes to the current branch:** Commit your changes first, then proceed.-- **Create a new branch and push changes there:** Preserve your work on a new branch.-- **Discard these changes:** Throw away your uncommitted changes to accept what's in Git.+- **Merge the remote changes into your local content:** Only offered when the changes merge cleanly.+- **Create a new branch and push changes there:** Saves your work to a new branch.+- **Force push to [branch], discarding and overwriting everything (can't be undone):** Overwrites the remote branch with your local content.+- **Delete unsynced changes (can't be undone):** Throws away your uncommitted changes to accept what's in Git.When in doubt, create a new branch and push changes to that branch. That way you won't lose any work.@@ -478,7 +460,7 @@ When in doubt, create a new branch and push changes to that branch. That way youIn Read-only mode, you can set Metabase to auto-sync changes from your main branch.1. Navigate to **Admin** > **Settings** > **Remote sync**.-2. Enable Auto-sync with Git.+2. Enable **Auto-sync with git**.By default, Metabase will check for and pull changes from the branch you specify every five minutes. You can also manually sync as needed.diff --git a/docs/installation-and-operation/serialization.md b/docs/installation-and-operation/serialization.mdindex 68426d88a86..23718092430 100644--- a/docs/installation-and-operation/serialization.md+++ b/docs/installation-and-operation/serialization.md@@ -306,7 +306,7 @@ Type: Boolean.Default: Data model is included.-Excludes [table metadata](../data-modeling/metadata/managing-tables.md) settings, which admins define in **Data Studio > Data structure**. Excluding the data model is useful for subsequent exports where you only want content changes.+Excludes [table metadata](../data-modeling/metadata/managing-tables.md) settings, which admins define in **Data Studio > Connected data**. Excluding the data model is useful for subsequent exports where you only want content changes.### Include field valuesdiff --git a/docs/questions/metrics-explorer.md b/docs/questions/metrics-explorer.mdindex 96bfc076da5..31895cdfbb1 100644--- a/docs/questions/metrics-explorer.md+++ b/docs/questions/metrics-explorer.md@@ -40,7 +40,7 @@ To return to the metric's home page, click the metric card in the search bar andTo open a **measure** in the metrics explorer:-1. Navigate to the measure in **Data studio > Tables > [Your table] > Measures**.+1. Navigate to the measure in **Data Studio > Connected data > [Your table] > Measures**.2. Select your measure.3. On the measure's page, click **three dots** next to the measure's name and select **Explore**.