Flow parameter list too long to see

[KUNGFUPANDA559]

i have a flow that has about 50 parameters being passed from powerapps.  Unfortunately, i cannot see the list and it's difficult to make out which parameter should be passed.  Is there a way to view the entire list, download the list, or some other alternative to view the information?

[Pstork1]

Rather than trying to manage 50 different parameters I would suggest consolidating the parameters into a collection and pass the collection as the parameter.  Then you can use the values in the collection inside the Flow where you need the specific parameters.

[Anonymous]

@Pstork1 

I'd be interested in how this could be done, would you have a basic code structure you could share to do this?

cheers

[v-xida-msft]

Hi @KUNGFUPANDA559 ,

Could you please share a bit more about your scenario?

Do you specified 50 parameters which needs to be passed from your app in your flow?

If you want to make all 50 arguments clearly within the 'FlowName'.Run() formula, I afraid that there is no way to achieve your needs in PowerApps currently.

As an alternative solution, I agree with @Pstork1 's thought almost. You could consider collect the data (you need to pass to flow) into a collection, then convert the collection data into a JSON String (using JSON function), then pass the JSON string into your flow.

So within your flow, you only need to specify single one parameter using "Ask in PowerApps" dynamic content within a "Compose" action. Then within your flow, you could use json function to convert the passed json string into a JSON table. Then you could add a "Apply to each" function, set above converted JSON Table as Input parameter value.

I have made a test on my side, please consider take a try with the following workaround:

Flow's configuration:

Then if you want to reference the column value from the converted JSON table within your own actions, please use the following expression:

item()?['Column1']

item()?['Column2']

item()?['Column3']

...

...

App's configuration:

Set the OnSelect property of the "Submit" button to following:

'FlowName'.Run(JSON(CollectionData))

More details about passing JSON value to flow, please check the following thread or video:

https://powerusers.microsoft.com/t5/Building-Power-Apps-Formerly/Pass-JSON-values-from-text-input-to...

https://www.youtube.com/watch?v=HLdOO4JPZ2I

Best regards,

[Pstork1 · Accepted solution]

Here's a simple example that demonstrates the concept. I created an app in Power Apps that accepts a text string, a number, and a date as input.

The On

Select for the button creates a collection containing one record with each of the values as a field.  That collection is then passed to the Flow as JSON using the JSON function to convert it to an array of values. Here's the code:

ClearCollect(ToFlow,{Text:TextString.Text,Number:Value(TextNumber.Text),Date:DatePicker1.SelectedDate});'PowerApp->Initializevariable'.Run(JSON(ToFlow))

 Then in the Flow I retrieve the string. Run the flow once to get a sample of the JSON string being passed using a variable to receive the string.  Then take that sample and use it in a Parse Json action to convert the JSON string back into an array of variables.  Each value will then be available in the dynamic content menu.  Since the JSON is passed as a string you may have to convert numbers and dates into the proper variable types.  Here's the simple Flow I used.

[Anonymous]

@Pstork1 @v-xida-msft  Thank you both. I will definitely be putting these solutions in my dev notes!

[v-xida-msft]

Hi @Anonymous ,

Have you taken a try with the solution I provided above?

Based on the needs that you mentioned, I think the solution I provided above could achieve your needs. Please consider take a try with it, then check if the issue is solved.

If you have solved your problem, please consider go ahead to click "Accept as Solution" to identify this thread has been solved.

Best regards,

[Anonymous]

@v-xida-msft  My comment was for personal research only. It was @KUNGFUPANDA559  who originally asked the question and this post is his to check as solve, I guess.

Thanks agin for the above solution though, it may yet come in handy 🙂 

[KUNGFUPANDA559]

Thanks @Pstork1 definitely adding this to my bag of tricks!