Unanswered

Empty PowerApps Collection

(0) Share

Report

Posted on by kona134

Hi,

I'm currently having a problem with my Power Automate flow, which is connected to a PowerApp. The PowerApp itself is working fine (it's writing to the data source reliably), so I figure there must be a problem with the flow.

The issue is that when the user hits 'Submit', using the Power Apps (V2) trigger, the collection it gathers shows as empty. This is more of a PowerApps thing, but I know the collection isn't empty in the App as I've disabled the Submit button if the collection is empty. Anyway, see below:

I've switched from the new designer to classic/old designer and hopefully that may have been the problem, but I'm stumped. Any help would be greatly appreciated!

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

Pstork1 68,707 Most Valuable Professional on at

Like (0)

Report

Can you show the Run formula you are using in Power Apps? The problem is that the v2 trigger doesn't have a data type for a collection, so you need to send the collection as JSON text and then do a Parse JSON on it in the Flow to get it back to an array of objects.

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No
kona134 67 on at

Like (0)

Report
Sure, the run formula is:

LoadEvalAppSendSP.Run( JSON( collection2, JSONFormat.IgnoreBinaryData & JSONFormat.IgnoreUnsupportedTypes ), JSON(varRoute), JSON(displayName) ));

And the rest of the flow looks like this (after the PowerApps V2 trigger):

Was this reply helpful? Yes No
kona134 67 on at

Like (0)

Report

After further investigation, I think it's because the trigger condition isn't reading the inputs correctly. Example below:

varRoute and collection2 are switched.

The order of this in the .Run sequence is the same as the in the flow, but I'm confused as to why the trigger condition isn't reading the inputs correctly?

Was this reply helpful? Yes No