From b87a36a98c4807b09649942604da8ffec75a8d91 Mon Sep 17 00:00:00 2001 From: camronbute-lantern Date: Wed, 15 Oct 2025 13:19:09 -0600 Subject: [PATCH 1/6] Fix formatting of autobinding explanation in docs --- .../deployment-pipelines/understand-the-deployment-process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/cicd/deployment-pipelines/understand-the-deployment-process.md b/docs/cicd/deployment-pipelines/understand-the-deployment-process.md index 93f393624e..384aa19622 100644 --- a/docs/cicd/deployment-pipelines/understand-the-deployment-process.md +++ b/docs/cicd/deployment-pipelines/understand-the-deployment-process.md @@ -118,7 +118,7 @@ Autobinding works only with items that are supported by deployment pipelines and ### Autobinding across workspaces -Deployment pipelines automatically binds items that are connected across pipelines, if they're in the same pipeline stage. When you deploy such items, deployment pipelines attempts to establish a new connection between the deployed item and the item connected to it in the other pipeline. For example, if you have a report in the test stage of pipeline *A* that's connected to a semantic model in the test stage of pipeline *B*, deployment pipelines recognizes this connection. +Deployment pipelines automatically binds items that are connected across workspaces if they're in the same pipeline stage. When you deploy such items, deployment pipelines attempts to establish a new connection between the deployed item and the item connected to it in the other pipeline. For example, if you have a report in the test stage of pipeline *A* that's connected to a semantic model in the test stage of pipeline *B*, deployment pipelines recognizes this connection. >[!NOTE] >Each pipeline must have the same number of stages. So for example, if pipeline *A* has 3 stages, then pipeline *B* must also have 3 stages. Pipeline *A* cannot have 3 stages and pipeline *B* 5 stages for autobinding to succeed. From 004e040cc801eca31661f8c41d42265c2dc426bd Mon Sep 17 00:00:00 2001 From: camronbute-lantern Date: Wed, 15 Oct 2025 13:21:10 -0600 Subject: [PATCH 2/6] Correct autobinding description in deployment process --- .../deployment-pipelines/understand-the-deployment-process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/cicd/deployment-pipelines/understand-the-deployment-process.md b/docs/cicd/deployment-pipelines/understand-the-deployment-process.md index 384aa19622..6dac5a6904 100644 --- a/docs/cicd/deployment-pipelines/understand-the-deployment-process.md +++ b/docs/cicd/deployment-pipelines/understand-the-deployment-process.md @@ -118,7 +118,7 @@ Autobinding works only with items that are supported by deployment pipelines and ### Autobinding across workspaces -Deployment pipelines automatically binds items that are connected across workspaces if they're in the same pipeline stage. When you deploy such items, deployment pipelines attempts to establish a new connection between the deployed item and the item connected to it in the other pipeline. For example, if you have a report in the test stage of pipeline *A* that's connected to a semantic model in the test stage of pipeline *B*, deployment pipelines recognizes this connection. +Deployment pipelines automatically binds items that are connected across pipelines if they're in the same pipeline stage. When you deploy such items, deployment pipelines attempts to establish a new connection between the deployed item and the item connected to it in the other pipeline. For example, if you have a report in the test stage of pipeline *A* that's connected to a semantic model in the test stage of pipeline *B*, deployment pipelines recognizes this connection. >[!NOTE] >Each pipeline must have the same number of stages. So for example, if pipeline *A* has 3 stages, then pipeline *B* must also have 3 stages. Pipeline *A* cannot have 3 stages and pipeline *B* 5 stages for autobinding to succeed. From 2ac0f0ebdea5920c9237c9286c3f31cda7f33429 Mon Sep 17 00:00:00 2001 From: camronbute-lantern Date: Wed, 15 Oct 2025 13:49:27 -0600 Subject: [PATCH 3/6] Fix grammar in deployment process documentation --- .../deployment-pipelines/understand-the-deployment-process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/cicd/deployment-pipelines/understand-the-deployment-process.md b/docs/cicd/deployment-pipelines/understand-the-deployment-process.md index 6dac5a6904..ddf580b352 100644 --- a/docs/cicd/deployment-pipelines/understand-the-deployment-process.md +++ b/docs/cicd/deployment-pipelines/understand-the-deployment-process.md @@ -202,7 +202,7 @@ The workspace content is shown in Deployment pipelines as a flat list of items. In Deployment pipelines, folders are considered part of an item’s name (an item name includes its full path). When an item is deployed, after its path was changed (moved from folder A to folder B, for example), then Deployment pipelines applies this change to its paired item during deployment - the paired item will be moved as well to folder B. If folder B doesn't exist in the stage we're deploying to, it's created in its workspace first. Folders can be seen and managed only on the workspace page. -With the current view of the folders hierarchy, you can select for deployment, only items in the same folder level. You cannot select items across folders. +With the current view of the folders hierarchy, you can select for deployment only items in the same folder level. You cannot select items across folders. Flat list view of deployment pipelines allows you to select items regardless of its location. With the flat list view, you can select items across folders, regarding their location in the workspace. For more information, see [flat list view](deploy-content.md#flat-list-view). From 92d47f13b25911a61baa6e2d76a2f7a371a9482a Mon Sep 17 00:00:00 2001 From: camronbute-lantern Date: Wed, 15 Oct 2025 13:50:23 -0600 Subject: [PATCH 4/6] Clarify flat list view description in deployment process --- .../deployment-pipelines/understand-the-deployment-process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/cicd/deployment-pipelines/understand-the-deployment-process.md b/docs/cicd/deployment-pipelines/understand-the-deployment-process.md index ddf580b352..1be1492c22 100644 --- a/docs/cicd/deployment-pipelines/understand-the-deployment-process.md +++ b/docs/cicd/deployment-pipelines/understand-the-deployment-process.md @@ -204,7 +204,7 @@ In Deployment pipelines, folders are considered part of an item’s name (an ite With the current view of the folders hierarchy, you can select for deployment only items in the same folder level. You cannot select items across folders. -Flat list view of deployment pipelines allows you to select items regardless of its location. With the flat list view, you can select items across folders, regarding their location in the workspace. For more information, see [flat list view](deploy-content.md#flat-list-view). +The flat list view of deployment pipelines allows you to select items regardless of its location. With the flat list view, you can select items across folders regardless of their location in the workspace. For more information, see [flat list view](deploy-content.md#flat-list-view). ### Identify items that were moved to different folders From ed06796904f6f8033ac4f23570c31d5934ea23a8 Mon Sep 17 00:00:00 2001 From: camronbute-lantern Date: Wed, 15 Oct 2025 13:51:03 -0600 Subject: [PATCH 5/6] Fix typo in parent-child item representation section --- .../deployment-pipelines/understand-the-deployment-process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/cicd/deployment-pipelines/understand-the-deployment-process.md b/docs/cicd/deployment-pipelines/understand-the-deployment-process.md index 1be1492c22..4b30163084 100644 --- a/docs/cicd/deployment-pipelines/understand-the-deployment-process.md +++ b/docs/cicd/deployment-pipelines/understand-the-deployment-process.md @@ -232,7 +232,7 @@ Unless there's also a schema change, the option next to the label to open a *Cha ## Parent-child item representation -Parent child relationships only appear in the new UI. They looks the same as in the workspace. The child isn't deployed but recreated on the target stage +Parent child relationships only appear in the new UI. They look the same as in the workspace. The child isn't deployed but recreated on the target stage :::image type="content" source="media/understand-the-deployment-process/parent-child.png" alt-text="Screenshot showing the depiction of a parent child relationship in the new UI."::: From 4abd9a553a6c72a1cae6addaa8d9eb4a4ce54aae Mon Sep 17 00:00:00 2001 From: camronbute-lantern Date: Wed, 15 Oct 2025 14:02:03 -0600 Subject: [PATCH 6/6] Update link for dataflow rules troubleshooting --- .../deployment-pipelines/understand-the-deployment-process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/cicd/deployment-pipelines/understand-the-deployment-process.md b/docs/cicd/deployment-pipelines/understand-the-deployment-process.md index 4b30163084..243a214965 100644 --- a/docs/cicd/deployment-pipelines/understand-the-deployment-process.md +++ b/docs/cicd/deployment-pipelines/understand-the-deployment-process.md @@ -311,7 +311,7 @@ Deployment pipelines supports [incremental refresh](/power-bi/connect-data/incre With deployment pipelines, you can make updates to a semantic model with incremental refresh while retaining both data and partitions. When you deploy the semantic model, the policy is copied along. -To understand how incremental refresh behaves with dataflows, see [why do I see two data sources connected to my dataflow after using dataflow rules?](/power-bi/create-reports/deployment-pipelines-troubleshooting#why-do-i-see-two-data-sources-connected-to-my-dataflow-after-using-dataflow-rules-) +To understand how incremental refresh behaves with dataflows, see [why do I see two data sources connected to my dataflow after using dataflow rules?](/fabric/cicd/troubleshoot-cicd#i-see-two-data-sources-connected-to-my-dataflow-after-using-dataflow-rules) > [!NOTE] > Incremental refresh settings aren't copied in Gen 1.