Return data to Powerapps issue

[Mike8]

Hello everyone,

I am following the instructions of this:
https://powerapps.microsoft.com/en-us/blog/return-an-array-from-flow-to-powerapps-response-method/

Unfortunately instead of retrieving the records, I retrieve a True value.

This is the flow:

Here is the expression that collects the data from the FlowAs you can see the flow sends back data
Here is what the flow returns
Does anyone know why? I would like to have the data and not the true value.
Thank you

[Anonymous]

These works for me.

Remove the old component, add updated one and it should work for you. Seems like PowerApp is not smart yet enough to detect changes for the components that were updated and by default when you created basic version it probably was sending Boolean value.

[tlmadison]

Thanks @Anonymous but I have created like 4 flows to try to get this resolved - and no luck. And I am not a novice to Flow (Automate) or Power Apps. @microsoft please advice

[Anonymous]

I am experiencing the same issue when calling an api via custom connector directly from a powerapp and setting the response to a variable or collection. I have done this in the past without issue, but it appears that powerapps is unable to recognize the response data and only provides me with a true or false value indicating if the call was executed successfully.

Call being made upon button click:

ClearCollect(colGetClients, App.GetClients("application/json",{Hub: "H001", OpenOrdersOnly: "True"}));

Actual response shown via postman, custom connector testing, and Dev Tools > Network:

{

  "Client": "test"

}

What is actually set to collection:

just a true value. The same happens for other methods that return multiple records. The collection or variable simply shows true or false.

Any help is appreciated. This is an urgent issue. I am wondering is this could be related at all to the custom connector issues that Microsoft was experiencing 2 weeks ago in late 2019.

[hjaf]

I haven't read all the replies here. 

All to often I see the standard "can you give me a screenshot" question being flagged as a solution while not being very helpful.

Anyway I have found that there is some magic going on in PowerApps Studio when connecting to flow / powerautomate. 

It used to be so that you can go to data sources or flow actions and click refresh on the flow, this does not seem to be the case any more.

My solution was to create a new button and then select the flow as its on select property, this forces the studio to update what it expects the flow to return. You can delete the button again and it should work with the buttons that did not previously work 🙂

[sjoepcoup]

Maybe this will help you to fix the problem: 

you can select all columns that come from the json format

[jarellm]

Encountered the same issue... what solved it for me was explictly stating the expected content type

[KnoxLam]

hjaf's solution worked like a charm!

Adding a new button, then link it to ms flow instantly forced the button to see what kind of data the flow is supposed to return

Side note: Idk to what extend it matters but if anyone is trying to recreate the flow from scratch and in case you haven't yet tried the export function, might as well try exporting the flow and import it back first

Really, recreating a flow is very tedious

[Sherwin]

After trying all the ways posted here, what worked for my case is to regenerate the Response body schema (Generate from sample) in the HTTP response action. The expected result from the flow became visible in Power Apps afterwards.

[Rawpoint]

I am seeing the same as you 

[ColinU]

I am also having this same issue, even after deleting and re creating the flow several times.

Button press > triggers flow >flow runs successfully >Response has values > ClearCollect(myCollection, my Flow.run(Textinput.Text)) >no collection, only 'True'

Flow is Get Input from Powerapps > HTTP Get > Response

Does anyone have a solution or reason to why this is still an issue given the time since this thread was made? If I remove response from the flow and just past the HTTP body back to powerapps I get the json data as one long single. string which is of course totally useless. 

[Sherwin]

@ColinUcan you provide the screenshot of your flow content? also, have you populated the schema in the get http response action?

[FlowJoe]

Have you removed the Flow from your power apps sources and re-added the flow, sometimes caching causes an issue and returns only that the flow ran but not the returned data. 

[ColinU]

Hi All

I have got this issue resolved however sorry to say I do not know what single action fixed it, by the end of it I had basically made a new blank power app and re-creates the flow verbatim under a new name (not save as and then edit) I am leaning towards some kind of caching issue as pointed out. 

Is there a way to turn off caching? Because this has wasted several hours of testing /searching/googling all to find out you were doing it right the whole time and it was some server side nonsense causing all the headache. very frustrating. 

[jason_brown]

Solution for me was as follows:

• On the button, go to OnSelect, select all and cut the text in the function
• Click on Action, then select Power Automate
• Click on the Flow in the Data blade, it should say "Adding"
• When it has completed, paste the text you cut earlier back into the OnSelect function
• Run the process again by clicking the button and the correct information appears in the collection

[Magra]

Thanks. Exactly what I was looking for.
Removing the Flow vom PowerApps and adding it again worked for me as well.

[DragonLord]

tried all of these options. still comes back with boolean. trash !

[Bahalzamon]

Like most of you none of these options worked for me.

I worked on this for I would say half a day. =(

What worked for me was removing the required portion of the JSON.
Source: https://powerusers.microsoft.com/t5/Building-Flows/Parse-Json-in-Flow-to-PowerApps/m-p/354885/highli...

Sorry I do not know how to link to a specific post, but the poster is the 7th post, one of a couple marked as a solution in that post.

I essentially went to the bottom of my "Response Body JSON Schema" within my Response action and deleted everything highlighted in my image. This resolved the "true" response.

[Anonymous]

I also had the exact same problem, data was coming from Flow as boolean when it should of been record.

I recreated the flow from scratch. And it worked..

[AndKanPA]

I started not with a blank flow, but with this template:

This works for me.

Other way: Remove connection to flow and add it again. Otherwise CanvasApp oesnt read return values again.
But: All uses of this connection are removed and you have to add it on all places again.
Is there a possibility to synchronize flow return values?

Best regards,

AndKan.

[CCL_DanielLewis]

Ok all, I have found a practical solution that doesn't resolve stupid work arounds.

Firstly, every time you make a change to your flow, you will more than likely need to change the PowerApps connection. For this reason, I do all of my testing in a brand new blank app that I just don't save - as it is easier to blow it away after each change I make in Flow (I don't think I will ever get use to saying Power Automate lol)

So, the solution. This is JSON. So rather than looking for exact solutions in PowerAutomate forums I actually learnt about JSON as a whole, and that is how I came to the solution. For me, the issue came around the schema PAutomate was returning to PApps. When you use the Generate from sample, it will just use the "type": "array" - so when PApps gets this response it says "Yes, this is an array".

This had me pulling out my hair because I was returning an array of objects, and could see that in PAutomate, it just wasn't reflected in PApps!

To resolve this, you actually need to articulate what the items of the array are in the JSON Schema;

{
    "type": "array",
    "items": {
		"type": "object",
		"properties": {
			"resource": {
				"type": "string"
			},
			"key": {
				"type": "string"
			},
			"fields": {
				"type": "object",
				"properties": {
					"displayName": {
						"type": "string"
					},
					"barcode": {
						"type": "string"
					},
					"birthDate": {
						"type": "string"
					},
					"library": {
						"type": "object",
						"properties": {
							"resource": {
								"type": "string"
							},
							"key": {
								"type": "string"
							}
						}
					}
				}
			}
		}
    }
}

It is also worth noting, that you do need to make sure you remove any "Required" properties the "Generate from Sample" adds, as this will also cause issues....