Flow with When a record is selected trigger does not appear in model-driven app bug

(0) Share

Report

Posted on by Helpful

382

Hi All,

I have been creating flows using this trigger and I think there's a bug.

To do the steps below you'll need a model-driven app with the Account entity included to validate the behavior.

These steps result in failure for me:

From within a solution, create a new Flow - DO NOT HIT SAVE UNTIL ALL STEPS ARE COMPLETED
Select the "When a record is selected" trigger, choose Default environment and Account as entity
Add an action "Get a record" from the CDS (current environment) connection
Rename the trigger to "When an Account is selected"
Rename the action to "Get Account details"
Name the flow : "Flow Test 1"
Click Save
Immediately, you'll see that the trigger's name has been reverted
Go to model driven app, select an Account from a list and click the Flow button in the ribbon - "Flow Test 1" will not show

These steps result in success for me:

From within a solution, create a new Flow - DO NOT HIT SAVE UNTIL ALL STEPS ARE COMPLETED
Select the "When a record is selected" trigger, choose Default environment and Account as entity
Add an action "Get a record" from the CDS (current environment) connection
Name the flow : "Flow Test 2"
Click Save
Go to model driven app, select an Account from a list and click the Flow button in the ribbon - confirm "Flow Test 2" appears

Anyone also observing something similar?

Categories:

Building flows

I have the same question (0)

All responses (5)

Answers (0)

donalmc 304 on at

Like (0)

Report

This is driving me insane at the moment - flows with the CDS selected record trigger not appearing.
Another observation is that any time you leave a flow with the selected record trigger, you get the message about your changes not being saved.

Was this reply helpful? Yes No
donalmc 304 on at

Like (0)

Report

It definitely looks like the when a record is selected step should never be renamed.
The rename step is greyed out after first save and a 'Rename is not supported for this step' popup appears.

Was this reply helpful? Yes No
Helpful 382 on at

Like (0)

Report

Aha, I hadn't clicked on the little "i". Yeah, I'm not sure if my steps above totally reproduce an error... I'm just seeing annoying behavior now where a Flow may or may not show up in the app - sometimes it shows up the next day and sometimes never. That can't be the intended behavior.
I will say this for anyone working with these: do NOT build a Flow past the first action until it shows up in the app.

Was this reply helpful? Yes No
donalmc 304 on at

Like (2)

Report
Yep - with the 'When a record is selected' trigger, here is my current get it working steps:
In a solution, create a flow with a 'When a record is selected' trigger.
Add a 'Get Record' action (CDS current is fine).
Don't rename either of these steps
Save, close, publish and go for a walk - the flow can take up to 15 minutes to appear in the menu.
Really, what we need is the 'When a record is selected' trigger to be added to the CDS (current environment) list.

Was this reply helpful? Yes No
sips1 43 on at

Like (0)

Report

Hi,

I have found out that if when creating the flow I rename the Record is selected trigger then I don't see the flow appear for triggering in the model driven app. Even when left overnight.

If I delete the trigger and re-add without renaming then save the flow I see it available for triggering in the model driven app.

It seems we can not rename the Record is selected trigger.

Thanks,

Was this reply helpful? Yes No