Cloud flows are inactive when deployed from a Managed Dynamics 365 Solution

(0) Share

Report

Posted on by Johannes Braaksma @...

Hello,

We've got a strange situation. We've two cloud flows created in a Dynamics 365 solution. If we export the solution as a managed solution and we deploy it in another environment they are turned off. So we turn them on. If we make a change on one of the flows in the master environment and create a new managed solution. The flows in the "child" environment will be turned of after importing the new managed solution in that environment.

In the image below you can see our environment where we see problems. There are two "Base" environments for two specific projects. The first "Base" environment is the one with owner "Connect-it 365" and the second Base environment is the first one with owner "ViaData".

Screenshot-2021_2D00_01_2D00_19-at-13.46.38.png

I have the same question (0)

All responses (6)

Answers (1)

Suggested answer

meelamri 13,216 User Group Leader on at

Like (0)

Report

Hi,

Please check the connection reference component.

flow.microsoft.com/.../

docs.microsoft.com/.../general-availability-solution-capabilities

community.dynamics.com/.../using-connection-references-with-power-automate-and-common-data-service

Was this reply helpful? Yes No
Johannes Braaksma @... 45 on at

Like (1)

Report

Hi Mehdi,

Thank you for you very quick response. I've read the links you gave me. But I don't think that's the answer to this question.

We have a cloud flow created in a Dynamics 365 solution. The flow uses a "Common Data Service (current environment)" connection which is already a "Connection Reference".

Was this reply helpful? Yes No
Suggested answer

meelamri 13,216 User Group Leader on at

Like (0)

Report

Hi Johannes,

According to the document :

We are now releasing new functionality that improves the way solutions work. In particular, some flows that use Common Data Service can now be automatically activated after you import a solution to a new environment.

https://docs.microsoft.com/en-us/business-applications-release-notes/April19/microsoft-flow/general-availability-solution-capabilities#known-issues

Known issues

The new Common Data Service (Current Environment) capability is available for preview today and is rolling out globally soon.

Was this reply helpful? Yes No
Verified answer

meelamri 13,216 User Group Leader on at

Like (0)

Report

Hi,

Makers can use connection references in flows to share connections between flows. When a solution is imported, there will be a guided experience for providing new connections within the connection references, allowing the flows to run successfully after importation. The use of connection references will simplify application lifecycle management.

General availability Apr 2021:

docs.microsoft.com/.../use-connection-references-simplify-application-lifecycle-management

Was this reply helpful? Yes No
Johannes Braaksma @... 45 on at

Like (0)

Report

Sorry for my late response. I'am not sure that this is the case/solution. Except three of the fourteen all of them have a "Common Data Service (current environment)" connection. So my guess is that they are successful deployed using the new connection method as described in the document you gave me.

It's a shame that Microsoft don't offer a FAQ with information about the status of the deployment. For now it's just guessing. It maybe right that this isn't fully supported, but maybe something else gone wrong.

Was this reply helpful? Yes No
Johannes Braaksma @... 45 on at

Like (0)

Report

I don't know if I'm able to mark this question as unanswered or if I should start a new question because some more investigation of my side lead me to a more specific problem with the cloud flows.

The problem is specific to cloud flow with an unbounded actions (Dyn365 actions). I my case I did make two flows. One regular flow which had a recurring timer in it and when triggered it added a note in the annotations table. The second flow has also a recurring timer but tries to call a unbounded action. A call to this action triggers a plugin who creates a trace log entry. Both are working properly in the Source instance (unmanaged), but the one with an unbounded action does not start in the target instance (as managed solution). the one that creates a new annotation record works in both environments.

Was this reply helpful? Yes No