Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
We have an issue using Clone Patching of a Managed Solution.
A clone patch solution is exported from our Dev instance as a Managed Solution. Call it HS_1.
This HS_1 managed solution contains a number of Modern Flows (say Flow X and Flow Y).
This HS_1 managed solution is then imported to a managed environment/instance (Test) using the Legacy Solution import page in D365 (Settings > Solution).
The managed environment (Test) contains a base solution (call it HS_Base) that also contains Modern Flow X and Flow Y.
The HS_1 managed solution imports successfully to the managed environment (Test).
However, if I edit a Modern Flow (Flow X) in that managed environment (Test) and compare that same Flow X from our Dev environment, the changes we made in Flow X in our Dev environment is not committed in the other managed environment (Test) where we published the managed solution to. I have uninstalled that solution in Test and reimported again, no luck. The modern flows in the imported managed solution are not committing the change.
Is there something extra that I need to do in the Test environment in order to commit the change to Modern Flow X and Y contained in the imported Manage Solution (HS_1)?
So here is Dev01 Flow X:
Here is Test Flow X:
Could you please validate what are the layers for this flow?
Solutions layers for a flow:
I saw this behavior happening when a flow has on top the Active layer, meaning that the flow was edited directly on the environment what can happen if you have to reset the connections, for example.
If you have an Active layer in your Flow, two approaches can be followed to validate if the flow is updated:
Thank you in advance.
Yes, it has to do with the solution layer.
We are using CDS connectors where you specify the environment to use. Although we do select (Current), it seems when this Flow is published to another environment, the publication process stops the Flow so we need to go in to check the connectors and activate it. Doing this creates that customized solution layer. Publishing again on this instance prevents the new Flow from being active because the customized layer takes priority.
We do exactly what you suggested.
Note that there is actually a new set of CDS connectors where you don't need to specify the environment. They look like these:
We were informed that using these type of CDS connectors will not turn off the Flow when published to another instance.
Business Applications communities