Dataflows in managed solution in managed environment

(2) Share

Report

Posted on by Hilda Steyn

297

Previously, I had an unmanaged solution, in an unmanaged prod environment. Not ideal I know. I regularly added data to the dataverse tables through dataflows that were outside the solution.
Now we are rebuilding everything. I have an unmanaged dev environment with an unmanaged solution. I exported the solution as managed to my new prod environment which is also managed.
When I create a dataflow in the new prod environment, it shows it is publishing, but then nothing happens. No data is added and the new dataflow isn't in the list.
I then created the dataflow in dev as part of the solution, and exported the solution again.
In prod, I can see the dataflow inside the solution, but the publish is greyed out. I don't see the dataflow outside the solution.
How do I set up dataflows for a managed solution in a managed environment?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

sumit_artesian 261 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi @Hilda Steyn,

Once the dataflow is inside a managed solution, it becomes effectively read-only in prod. That’s why Publish is greyed out. Managed environments are meant to receive deployed components, not have them edited directly. However, you can still publish components that are in production environments by navigating to the Default Solution in the production environment, finding the dataflow, and publishing it from there.

Every component in your environment is added to the Default Solution by, for lack of a better word, default. And they remain unmanaged, which allows you to edit them as well as publish them. However, this is against Microsoft's best practices. Dataflows usually should not be included in the solution and should always be created in the target environment outside of solutions.

If a newly created dataflow disappears after publishing, I’d also check:

Whether the prod environment has proper Dataflow permissions/capacity

Whether the connection setup is failing silently during publish

Whether the environment is using modern dataflows vs legacy behavior

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item.

If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like! 🩷

Was this reply helpful? Yes No
Suggested answer

Haque 3,653 on at

Like
a
(1)

Report
Copy link

Link copied!
Hi @Hilda Steyn,

Let's circumvent this question "How do I set up dataflows for a managed solution in a managed environment?"

When we create a dataflow inside a managed solution in a managed production environment, it will not appear outside the solution because managed solutions lock down components to prevent direct editing or creation outside the solution context.

To set up dataflows properly for a managed solution in a managed environment, we can follow these best practices:

Create and Configure Dataflows in the Dev Environment: Let's build and fully configure the dataflows in proposed unmanaged dev environment where we have full edit rights.

Include Dataflows in the Solution: We then add the dataflows to the unmanaged solution in dev. This ensures they are part of the solution package.

Export as Managed Solution: Export the solution from dev as a managed solution for import into production.

Import Managed Solution into Production: Import the managed solution into the production environment. The dataflows will be included as managed components.

Publishing Happens on Import: The dataflows are published automatically during the managed solution import process. We cannot manually publish or edit them in production.

No Direct Edits in Production: Since the dataflows are managed components, you cannot create, edit, or publish them directly in production. All changes must be made in dev and redeployed.

Use Environment Variables for Connections: To handle environment-specific data sources, use environment variables or connection references in your dataflows. This allows the same solution to adapt to different environments without manual changes.

Validate After Import: After importing the managed solution, verify that the dataflows are published and connections are correctly set to production data sources.

Please let me know if these steps help.

Referece:

Solution concepts

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No