Answered

Passing a blank ou null value to Power Automate

(0) Share

Report

Posted on by PierreCA

364 Moderator

Hello,

I'm trying to pass a blank value to Power Automate from an empty input box to get a non-filtered list.
When I don't try to test the value. There's no error signal in the code, but I don't get the non-filtered list. It remains empty.

I've try different approaches to send an empty value, but all failed.

How could it be done?

Categories:

Building Power Apps

I have the same question (0)

All responses (7)

Answers (1)

Sort by

BCLS776 8,994 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

Have you tried making the input parameter in the call to the flow "optional" and then handling a blank input properly within the flow?

Bryan

Was this reply helpful? Yes No
PierreCA 364 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

Hello @BCLS776 (Bryan) ,

How do you make the input optionnal when calling the flow?

The flow is already set to handle a blank value.

Was this reply helpful? Yes No
BCLS776 8,994 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

You can edit it on the trigger operation in the flow:

Remember to save your flow, and then refresh it in the app before continuing.

Bryan

Was this reply helpful? Yes No
PierreCA 364 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

But when I test if the variable containing the input is empty or blank, i got an error message. How do you test the variable content?

Was this reply helpful? Yes No
BCLS776 8,994 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!
Please change the expression in Power Automate to:

empty(triggerBody()?['text'])

The '?' symbol is important in Power Automate - it indicates the field may or may not exist in triggerBody()

Also, the expression language used in Power Automate is different than PowerFx. Here's the reference

Hope that helps,

Bryan

Was this reply helpful? Yes No
PierreCA 364 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

Hello @BCLS776 ,

Your solution for the flow works.

But curiosily, the very same line of code in Power Apps, to call the flow has now an error? How to circumvent the problem?

Was this reply helpful? Yes No
Verified answer

BCLS776 8,994 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!
Now that the parameter is optional, it is handled a bit differently in the flow call:

TrouverNomEntite.Run({text: inputRechercheEntite.Text})

Was this reply helpful? Yes No