Result from flow (boolean)- comparing with boolean- gives Json parsing error

(0) Share

Report

Posted on by SLMR

518 Moderator

Hello to all of you,

i have different flows that "Respond to a powerapp or flow" with a boolean "success".

In the App i use:

Set(flowstatus,FlowToRun.Run())

If(flowstatus.success, XXX, YYY)

For some flows that works fine, for others it gives an json-parsing error: expected boolean got string.

In the flow the return variable is declared as boolean and the value is set with expression "true"

I can not figure out, why it sometimes wroks and sometimes not.

The flow runs fine. But just the comparison of the return value failes.

Any help is welcome.

Categories:

Building Power Apps

I have the same question (0)

All responses (5)

Answers (1)

Verified answer

Michael E. Gernaey 53,315 Super User 2025 Season 2 on at

Like (2)

Report
Hi @SLMR

Its a little difficult because I do realize that you are saying it works for others, but we cannot see how those are configured.

Also, when this happens, do you go look at the Flow run, to see what exactly happened In the flow run and if instead it returned an Error? versus what you thought would happen?

Lastly, when it happens, do you go to the Variables sections and look at what the value is? Because that would tell you exactly what the Set variable was set to??

That being said can I make a suggestion. Instead of using Set(variable, XXXX.Run())
Can you do
ClearCollect(flowResult, Flow.Run()); // please fill in your flow information
Then use First(flowResult).status to check it.
But again, if you have an issue with the result value, please please please if you can go to the Variables section to look at what was passed back

In your example (popup) you could have gone to look at it, to see the value.
Click the ... next to settings
Click Open
Click Variables (if you use Set) or Click Collections (if you use the collection) BTW I dont mind which one you use, I am just giving you options. The important part is looking at the flow to see where it ended and then the variable value itself.

If you like my answer, I would really appreciate if you please Mark it as Resolved, and give it a thumbs up, so it can help others

Cheers

Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

Was this reply helpful? Yes No
SLMR 518 Moderator on at

Like (0)

Report

Thanks for the quick and helpfull answer.
Inspecting the varible shows me that the flow returns something other than expected.
Although the flwo does exactly waht it should do.
And when testing the flow and inspecting the rest there, it should return other values.

I had some difficulties with the flow, as i changed a parameter/variable in the flow "Ask in power app".
And now the flow wanted two variables.
- Even after:
- deleting the connection from the app to the flow
- Deleting the step "initialize variable" and all references to the variable in the flow.
Everytime i start the flow it wants the varible that is no longer asked for and not used in the flow.

But so i just started the flow with two paramters with the same value and the flow runs fine.
But maybe that cases a problem that i can not see.

At least i can now analyze where the problem might come from.
Thanks a lott and have a nice weekend

Was this reply helpful? Yes No
Michael E. Gernaey 53,315 Super User 2025 Season 2 on at

Like (0)

Report

Hi @SLMR

You as well. It does sound like you are using maybe the Power Apps (V1), it won't say V1, thats how you know.

If you are, I would expect weird things like you have. Instead please Delete that Trigger and Add the Power Apps (V2) and define your input directly.

You'll be way happier, especially when V1 goes away

If you like my answer, I would really appreciate if you please Mark it as Resolved, and give it a thumbs up, so it can help others

Cheers

Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

Was this reply helpful? Yes No
SLMR 518 Moderator on at

Like (1)

Report

Yes this is still the old V1 trigger.
I will change all my flows to V2

Was this reply helpful? Yes No
SLMR 518 Moderator on at

Like (0)

Report

Hy @FLMike

i could get it working, but there seems to be some problem with boolean variables.

I returned two variables from the flow "success" as boolean and "info" as string.
While the info is returned in the right way, i got an arror message for the boolean type i can not understand:
Any idea?

Was this reply helpful? Yes No