Unanswered

Branching with Premium Response

(3) Share

Report

Posted on by danielleh

So I built a flow with a "Response" sending data back to my app on the main/linear path. It's the one named "Response." I then wanted to use the action to send a different response back if it takes a different path that's the one "Delete - Response - copy new schema" and then terminate the flow if this is the path it takes. When I run my glow the actions all trigger document status is checked, items deleted etc.

But the "Delete - Response - copy new schema" does not send data back into my PowerApp canvas. I always get back a varStatusCode = blank on this branch. The only way I've been able to get it to work is to only have the main "Response" send the data back.

This is not the optimal way I want to run this because the "Get updated item" will fail when the "Delete" branch runs. And I know I can tell it run on skip, fail etc. But I rather not. Is there a work around for this?

Categories:

Building flows

Screenshot 2025-0...

Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

I have the same question (0)

All responses (9)

Answers (1)

abm abm 32,865 Most Valuable Professional on at

Like (0)

Report

Hi

Need to see the flow. The attachment screenshot status says its still under scan. Just to let you know that you can copy a screenshot and paste with your content. This is much easier than attachment.

Thanks

Was this reply helpful? Yes No
danielleh 47 on at

Like (1)

Report

@abm abm thank you just posted it above

Was this reply helpful? Yes No
eliotcole 4,363 Moderator on at

Like (0)

Report

If you are responding to a PowerApp (or a parent flow in a Solution) you do not need the premium actions, use the action with the "Respond to a Power App or flow" name.

It looks like this in the actions menu:

... and like this in a flow. :-)

Was this reply helpful? Yes No
danielleh 47 on at

Like (1)

Report

@eliotcole Thank you. Yes I know there is the other option besides the Premium Response. I formerly used the "Respond to Power App" but there's a limitation of data to take back in as it only allows I think 20 fields to be input. So I find it easier to use the premium response. Also there are limitations with the "Respond to Power Apps" because it uses status code: 200 and then you can't send back different data (didn't add date just showing that it sets the statusCode to 200 on the back end) so then you can't use multiple different schemas because it expects the schema to be the same with the same status code.

Here's the amount of data for this one flow I'm sending back. This is nice because it enters the app and I have it update the modified item. This status code is set to 200 but I've been able to add multiple premium Responses on different branches by changing the status code and have some as 201, 400, 403 etc.

So the main issue is just that the flow runs fine and all actions are completed but the Response doesn't trigger on the branches just the linear path. I guess I'm just wondering if this is a known limitation or if I'm doing something wrong.

Was this reply helpful? Yes No
eliotcole 4,363 Moderator on at

Like (0)

Report

Heya, @danielleh, you can brute force your way in to making the response a LOT more functional.

I have managed to do this before, but it takes a fair bit of doing ... either by good old copy/paste and editing elsewhere ... or by editing the flow definition using the flow management actions.

Either way, good luck with your quest!

Was this reply helpful? Yes No
danielleh 47 on at

Like (1)

Report

@eliotcole hey thanks. Yea, I'm not having an issue with the bottom Response working just an issue with the branched Response working.

Was this reply helpful? Yes No
Verified answer

eliotcole 4,363 Moderator on at

Like (2)

Report

Well, @danielleh, my original response to this was going to be set one single (premium) Http Response, and fill it with an object variable.

Then ... set that variable in each rung of your switch.

That will basically allow you to put whatever you like in there. :-)

EDIT - Here's a visual representation of what I mean ... essentially, you would be using variables for what they should be used for. :)

Was this reply helpful? Yes No
danielleh 47 on at

Like (1)

Report

@eliotcole got it!

Thanks that what I had been doing and wanted to see if there was a different way. Just because the schemas can be different on different branches and I wanted to avoid having to have long portions of the flow have run-on setting set to run on fail and skip.

But if this is the best/only way then I'll make due with it. I was hoping to have the Response on a branch and then just terminate the flow.

Was this reply helpful? Yes No
eliotcole 4,363 Moderator on at

Like (0)

Report

Nice one, @danielleh, glad you got there in the end!

Apologies for giving you a little to do yourself, but I like to try to give you something that will let you pick some of it up as you're doing it ... if that makes sense?

Plus ... if all else fails ... I'm sure that there's a method on the PowerApp side to 'jsonnify' some text (like the json() expression in Power Automate & Logic Apps) so you could just push a JSON object over as a string or base64 encoded string, maybe? I dunno!! :sweat_smile:

Was this reply helpful? Yes No