Unanswered

Flow Not Displaying in Model-Driven App

(0) Share

Report

Posted on by NathanWill

Hi, All-

I created a Flow with Common Data Server Steps for (1) When a record is Selected (2) Get record (3) Create a new record. I'm using these to provide copy/clone functionality within Dynamics. My issue is that the Flow is available when I use the legacy Dynamics interface, but it does not show when I use my Model-Driven App (Unified Interface). The Flow has successfully run multiple times, but it isn't available for me or my other users in the Model-Driven App. Is this a bug or am I missing some additional setup that is required for Model-Driven Apps?

Legacy Dynamics Interface:

Model Driven App:

Categories:

Using flows

I have the same question (0)

All responses (7)

Answers (1)

v-alzhan-msft on at

Like (0)

Report

Hi @NathanWill ,

Please take a try tp choose only one record before you click the Flow botton for running the flow.

Best regards,

Alice

Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Was this reply helpful? Yes No
NathanWill 13 on at

Like (0)

Report

Unfortunately, that is not a solution. In the legacy UI I can select one or many records and Flow works. In the Model-Driven App Flow does not (login) work regardless of whether I select one or many records.

Was this reply helpful? Yes No
NathanWill 13 on at

Like (0)

Report

@Stephenand @CWesener - I see both of you have had insights on similar posts in the past. Do you have any ideas on what I'm missing on this one?

Thanks!

Was this reply helpful? Yes No
BusyIntelligence 321 on at

Like (0)

Report

I have the same issue in my Sandbox while everything's fine on the Production instance.
I noticed my Flow does appear when I deactivate all on-demand old school workflows on this entity.
As my Sandbox has wave 2 enrolled I hope this behaviour is not also on my Prod instance after this weekend...
Keep my fingers crossed....

By the way, this error only happens when the user runs Dynamics in Dutch language, which is the base language of the instance. When running English, German or French, the Flow appears like it should.

Was this reply helpful? Yes No
Verified answer

BusyIntelligence 321 on at

Like (0)

Report

In my previous reply I mentioned I had this same issue on my Sandbox (wave 2) and not on production.
This weekend wave 2 was enrolled on both instances and my issue is gone now.
Flows are available on all instances, all languages etc.
They still work only in a browser, not on Win10 app or Android App, but that's another story I'm afraid.

Was this reply helpful? Yes No
NathanWill 13 on at

Like (0)

Report

Thanks for the feedback, @Maurits. I am scheduled to enroll in Wave 2 this weekend so I'll report back if it resolves the issue for me too.

Was this reply helpful? Yes No
NathanWill 13 on at

Like (0)

Report

The week immediately after our org was enrolled in Wave 2 this didn't function as expected, but after revisiting several weeks later the issue seems to be resolved. I can now access my Flows from a View in a Model-Drive app.

Was this reply helpful? Yes No