Unanswered

Condition in Approval Flow (outcome based on optional input at trigger) failing

(0) Share

Report

Posted on by lorinda_abey

I have an approval flow with an optional text input ("Message") at the trigger step.

In order to be able to include the message in an email later on in the flow without the flow failing (in the scenario the field is left blank), I have created a sequence of steps including initializing a variable, adding condition that checks if the message is null and then appending the string variable accordingly:

I then use the variable in my email message body.

This has worked perfectly for 2 approval flows, created late last year, which have been used by my team since January.

Today I tried to create another separate flow with the exact same steps / parameters and it is failing. I can't figure out why. Below is the error message I am getting:

I've gone back and retested the other 2 flows and confirmed everything is still working with these. I've also done a side by side check of the code behind the condition step. There are no differences between the one that works and the one that fails.

Any ideas what is going wrong?

Categories:

Building flows

I have the same question (0)

All responses (5)

Answers (0)

Sort by

v-yetonggu-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!
Hi @lorinda_abey ,

Please show you a screenshot of the configuration in the trigger that causes your error.

And you can put this expression to the left of the condition:

triggerBody()['entity']

Best Regards,

Sunshine Gu

Was this reply helpful? Yes No
lorinda_abey 41 on at

Like (0)

Report
Copy link

Link copied!

Not sure what you mean by configuration?

The second image in my original post shows the condition step that is failing. It uses the dynamic content "Message" from the trigger and checks if it is equal to null.

Was this reply helpful? Yes No
v-yetonggu-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @lorinda_abey ,

This error message indicates that the title of the text field entered in your trigger is not 'text'.

The configuration screenshot I want to see means the individual parameters in your trigger.

Like this:

Best Regards,

Sunshine Gu

Was this reply helpful? Yes No
lorinda_abey 41 on at

Like (0)

Report
Copy link

Link copied!

Still confused. The first image in my post shows the screenshot of the trigger from one of the flows.

Posting another below:

Was this reply helpful? Yes No
lorinda_abey 41 on at

Like (0)

Report
Copy link

Link copied!

I had identified the issue but I am still unclear why it is working in my old/existing flows and not working in this new one I am building.

The issue seems to be that if no text is input at the trigger step, the raw output of the trigger has no "text" parameter:

As the condition step is checking if "@triggerBody()?['text']" is equal to "@null", it is failing because no "text" exists.

My previous flows seem to be able to handle this without throwing up an error which is what makes it so confusing!

I have resolved the error by adding in a Compose step with input: @{triggerBody()?['text']}. I am then using the Output from this Compose step in my Condition step:

New flow now works.

If anyone can still tell me why it worked before, I'd appreciate it. I don't like mysteries!

Was this reply helpful? Yes No