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: dependencies polish (#65754)
Alex Yaroshbef0a89f9f71
diff --git a/docs/data-modeling/images/check-dependencies.png b/docs/data-modeling/images/check-dependencies.pngnew file mode 100644index 00000000000..709588a0c63Binary files /dev/null and b/docs/data-modeling/images/check-dependencies.png differdiff --git a/docs/data-modeling/models.md b/docs/data-modeling/models.mdindex 16fe77cc02d..a7db5178517 100644--- a/docs/data-modeling/models.md+++ b/docs/data-modeling/models.md@@ -121,9 +121,13 @@ You can edit a model's query by clicking on the down arrow next to the model's n### Checking for breaking changes-> {% include plans-blockquote.html feature="Checking for breaking changes" %}+{% include plans-blockquote.html feature="Checking for breaking changes" %}-When you save changes to a model, Metabase will try to detect whether your changes would break any other entities that depend on that model. For example, if you remove a column from the model, but other questions based on that model rely on that column, Metabase will warn you that those downstream questions will break.+When you save changes to a model, Metabase will try to detect whether your changes would break any other entities that depend on that model. For example, if you remove a column from the model, but other questions based on that model rely on that column, Metabase will warn you that those downstream questions will break.++++Currently, Metabase will look for broken column references. If you rename or remove a column, Metabase will likely flag the change as breaking downstream entities. But Metabase can't detect other types of changes like changing the column type or computation logic as breaking changes.## Model list view@@ -131,7 +135,6 @@ When you save changes to a model, Metabase will try to detect whether your changList view helps you explore records one by one instead of sorting through big tables. You can customize the layout to highlight the most important fields.-To view a model as a list:1. Visit the model.diff --git a/docs/questions/images/check-dependencies.png b/docs/questions/images/check-dependencies.pngnew file mode 100644index 00000000000..709588a0c63Binary files /dev/null and b/docs/questions/images/check-dependencies.png differdiff --git a/docs/questions/introduction.md b/docs/questions/introduction.mdindex 82281d8c3d2..9a1f388e44c 100644--- a/docs/questions/introduction.md+++ b/docs/questions/introduction.md@@ -56,9 +56,13 @@ Questions saved to a collection can be added to multiple dashboards. Moving a qu### Checking for breaking changes-> {% include plans-blockquote.html feature="Checking for breaking changes" %}+{% include plans-blockquote.html feature="Checking for breaking changes" %}-When a question, model, or metric is saved, Metabase will try to detect whether the changes you made would break any dependent entities. For example, if you removed a column from a question that other questions rely on, Metabase will warn you that those downstream questions will break.+When a question, model, or metric is saved, Metabase will try to detect whether the changes you made would break any dependent entities. For example, if you removed a column from a question that other questions rely on, Metabase will warn you that those downstream questions will break.++++Currently, Metabase will look for broken column references. If you rename or remove a column, Metabase will likely flag the change as breaking downstream entities. But Metabase can't detect other types of changes like changing the column type or computation logic as breaking changes.## Moving questions from collections to dashboards (and vice versa)