Answered

IfError is skipping step - help

(0) Share

Report

Posted on by HarchR

Hi Hope someone can help nd point out where I am making a mistake.

I have a flow in a canvas app wrapped in an IfError function and inide that a Set functionto store the error as a variable.

When the flow responds with an error, only the final step in the [IF] condition (highlighted in screenshot) is executed. The first step which I understand should be executed when an error is detected is skipped or doesn't stop the processing. Hope someone can help.

The code basically sets context variables to true to show status panels in the app. The Upload success panel gets shown despite an error being generated.

Visible property of UploadError container:

Visible property of UploadSuccess container:

I tried using an [And] operator as I thought i might be using too many steps but that shows the error panel when there is no error generated.

Categories:

Building Power Apps

All responses (6)

Answers (1)

Sort by

JasonZF 572 on at

Like
a
(0)

Report
Copy link

Link copied!
I never really liked IfError(), because I've had issues with it as well in the past. In this type of scenario, I prefer using a normal If() statement with the first value (your Set() function) surrounded by IsError(). Try this out and see if it works.
If( IsError( Set( varFlowRunStatus, UploadAgreementDocument.Run( ... ).flowrunstatus, ) ), UpdateContext( { locShowUploadSpinner: false, locShowUploadError: true } ), UpdateContext( { locShowUploadSpinner: false, locShowUploadSuccess: true } ) )
HarchR 26 on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks for your help I appreciate it. Unfortunately that doesn't work. It still skips to the last rule for showing a success panel when an error is generated.

I'll keep trying to find some way of working around it an post here if I find a solution. Right now though I thin I may have to leave error handling out of the app to get it done and instead let the flow catch block do the notification by email. Not ideal but it's an option.
JasonZF 572 on at

Like
a
(0)

Report
Copy link

Link copied!

When you say your "flow responds with an error," what do you mean? Is this Power App somehow failing to communicate with the flow, or is the flow actually responding back, but with an error provided by a "Respond to PowerApp" action inside the flow? Is it possible that the Run() command in your Power App isn't actually failing?
Verified answer

HarchR 26 on at

Like
a
(0)

Report
Copy link

Link copied!

Right so after lots of frustration, I managed to work around this.

IsError didn't work for my scenario as it produced the same result: The [Else if] condition was always executed no matter what.

When the 'Upload' button is clicked, the flow is executed and responds with either "Success" or if it catches an error, it responds with the action and message text from the error JSON.

or

2. I stripped the IfError condition back to simple executing the flow and setting a variable called FlowRunStatus.

3. I then run another If condition where If the returned value in the variable is "Success", then execute a context variable, else, execute another.

3. The panels are then made visible depending which context variable is executed. I think the key here was moving the context variable execution out of the function that runs the flow and checks for a response.

It's not the cleanest or most elegant way to run this as i would have liked but deadline for testing looms and it works.

Final code below in case it helps anyone else with a similar issue:

Thanks to those that tried to help. Appreciated as always!

@JasonWS I will start sing IsError instead of IfError from now on. Hopefully have more luck with it going forwards.
JasonZF 572 on at

Like
a
(0)

Report
Copy link

Link copied!

That's what I thought. Even though what you were intending to be returned from the flow to be an "error," PowerApps doesn't see that as an error, since the command was executed successfully. That's why the third parameter was always being executed.

I do something similar in my flows. I have a status being returned ("sucess"/"fail" texts) along with any needed information. The "fail" side of the flow just has blank values for anything else that's normally provided from the flow. I then have logic based on whether the status is = "fail" or "success". Glad it works out now. With some of my newer flows, I even have as much as I can inside a Scope block, that way if any step within fails, it'll still trigger the "fail" side's Respond to a Power App action.
HarchR 26 on at

Like
a
(0)

Report
Copy link

Link copied!

Useful thanks!