Moving Dataflows between Solutions - Dataflow cant be

[Sebastian030]

Hello there,

im working the first Time with the ALM Pipeline in Power Plattform and faced an unexpected behaviour where i couldnt find a solution online.

I created the following Items in my DEV Environment:
Dataflow1 - Table1, Dataflow2, Table2 and a Cloudflow1 that triggers Dataflow1, checks for errors and then triggers Dataflow2. The Data of each flow gets passed into a dataverse Table (Table1 and Table2).

After Testing the flows in the DEV Environment i succesfully changed all the variables in the Dataflows and the cloud flow to the PROD Environment.

I then created a solution in my dev environment, added the above named elements and used the pipeline feature to deploy the solution/items as "managed" to the PROD Environment.

Ive run the flow successfully in the DEV Enviroment and was happy, but then realized something was wrong.

At first i realized that the Cloudflow is still triggering the Dataflows in the DEV Environment, although i had changed the Environment in the Cloudflow. The Name of the CloudFlow that should be triggered was shown as an internal IDs.

i changed the name to the actual name of the dataflows and deployed the solution again.

Now the correct dataflow in the PROD Environment gets triggered by the Cloudflow, but it fails with the Error:

"A problem occurred while updating the dataflow, the dataflow was never published. Please publish the dataflow or fix all errors from previous publishing attempts by editing the dataflow and repeating the process."

The Dataflow was successfully published and executed in the DEV Environment.
In the PROD Environment the Dataflow is in a "managed Solution" and cant be published edited in the PROD Enviroment.

I really dont know how to fix this Problem, maybe i misunderstood the ALM Process for Solutions in the PowerPlattform?

Looking for any Help/ replies,

Greetings,
Seb

[gulshankhurana]

Hi @Sebastian030 

I'm not a dataflow expert but you could perhaps try 'publish all customisations' in dev and then export/import the solution. If it succeeds, then all sorted else 'publish all customisations' in target environment also once imported. If all works then we'd know for sure that there is an unmanaged layer in the target environment somewhere.

Kind regards

Gulshan

Please give it a thumbs up 👍🏻 if you appreciate my efforts.

If my answer helped you resolve your issue then please also mark it as a solution ✅  so that it helps others experiencing the same problem.

[PPCitDev · Accepted solution]

Hi Sebastian,

This mostly should get fixed if you edit the dataflows and republish / refresh them in the target environment. Dataflows don't use connection references and thus, it becomes an additional step to perform while importing a solution.

Hope this helps! Thank you!