From e33c21ff4cea2488576b076a42a5d5a1da47c3ed Mon Sep 17 00:00:00 2001 From: Alex Yarosh <alexandra@metabase.com> Date: Wed, 31 Jul 2024 08:51:33 -0400 Subject: [PATCH] docs: import clarification (#46328) --- docs/installation-and-operation/serialization.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/installation-and-operation/serialization.md b/docs/installation-and-operation/serialization.md index 0aacabf1fa3..5e35e3d281c 100644 --- a/docs/installation-and-operation/serialization.md +++ b/docs/installation-and-operation/serialization.md @@ -322,6 +322,8 @@ Metabase will not delete items from target instance during import, but it will o Metabase relies on [Entity IDs](#metabase-uses-entity-ids-to-identify-and-reference-metabase-items) to figure out which items to create or overwrite, and what are the relationships between items. When importing into an instance that already has some content in it, keep in mind: +- If you import an item with an `entity_id` that doesn't exist in your target Metabase, Metabase will create a new item. + - If you import an item with an `entity_id` that already exists in your target Metabase, the existing item will be overwritten. In particular, this means that if you export a question, then make a change in an exported YAML file — like rename a question by directly editing the `name` field — and then import the edited file back, Metabase will try to apply the changes you made to the YAML. -- GitLab