Forum Discussion
Deployement Pipelines - Dataflow with Gateways
Hello to all,
I have three REC/ACC/PROD environments.
And I want to deploy the Dataflow in REC on ACC and then PROD by changing the datasource.
So I added a parameter rule on the Dataflow to change the data source.
Howerver when I go into the Dataflow settings to match the data source with the gateway I have to match the old data source as well and this causes me problems in PROD as I cannot apply the gateways.
Hi Anonymous ,
You can refer to the limitations on data flow when deploying pipelines
-
When deploying a dataflow with linked entities that reside on the same workspace, the deployment will fail.
-
When deploying a dataflow to an empty stage, deployment pipelines creates a new workspace and sets the dataflow storage to a Power BI blob storage. Blob storage is used even if the source workspace is configured to use Azure data lake storage Gen2 (ADLS Gen2).
-
Service principal isn't supported for dataflows.
-
Deploying common data model (CDM) isn't supported.
-
For deployment pipeline rule limitations that effect dataflows, see Deployment rules limitations.
-
If a dataflow is being refreshed during deployment, the deployment will fail.
-
When comparing stages during dataflow refresh, the results are unpredictable.
Or when you have not parameterized the data source server and database, you need to map the "phantom" data source to a data gateway (and the same data gateway at that) as a valid data source.
You can refer to the threads to see if it helps：Dataflows deployed from a Deployment Pipeline - invalid data source
Community Support Team _ Caitlyn
If this post helps then please consider Accept it as the solution to help the other members find it more quickly.
-
1 Reply
Hi Anonymous ,
You can refer to the limitations on data flow when deploying pipelines
-
When deploying a dataflow with linked entities that reside on the same workspace, the deployment will fail.
-
When deploying a dataflow to an empty stage, deployment pipelines creates a new workspace and sets the dataflow storage to a Power BI blob storage. Blob storage is used even if the source workspace is configured to use Azure data lake storage Gen2 (ADLS Gen2).
-
Service principal isn't supported for dataflows.
-
Deploying common data model (CDM) isn't supported.
-
For deployment pipeline rule limitations that effect dataflows, see Deployment rules limitations.
-
If a dataflow is being refreshed during deployment, the deployment will fail.
-
When comparing stages during dataflow refresh, the results are unpredictable.
Or when you have not parameterized the data source server and database, you need to map the "phantom" data source to a data gateway (and the same data gateway at that) as a valid data source.
You can refer to the threads to see if it helps：Dataflows deployed from a Deployment Pipeline - invalid data source
Community Support Team _ Caitlyn
If this post helps then please consider Accept it as the solution to help the other members find it more quickly.
-