Unanswered

Issue getting Boolean into Powerapps with Flows

(1) Share

Report

Posted on by Arcr0s

Hello everybody,

I have finally run into an issue which I can not seem to fix. I am working on an application which generates pdf files based on info entered in the app. I have Flow working like a charm generating the PDF file when initiated from Powerapps, and the file is sucessfully created. However I wanted to implement a Flow to check if the file name the user is trying to use is not already taken. I got that Flow working perfectly aswell. This is where I ran into an issue. No matter what I try I can not get PowerApps to read the returned boolean although im pretty sure it should.

Code in my OnChange of the Title TextBox
haspdf is the boolean returned by the flow 

UpdateContext({hPdf:'PowerApps-Schaltfläche–2'.Run(txtDocTitel.Text).haspdf});;Notify("" & hPdf)

I also tried

UpdateContext({hPdf:'PowerApps-Schaltfläche–2'.Run(txtDocTitel.Text)});;Notify("" & hPdf.haspdf)

I have tried using Set aswell as directly calling the flow when pressing the submit button. Maybe someone knows what I am doing wrong. Any help would be appreciated 🙂

Categories:

Building Power Apps

I have the same question (0)

All responses (2)

Answers (0)

poweractivate 11,078 Most Valuable Professional on at

Like (0)

Report
@Arcr0s

Remove the two semicolons, should really be just one semicolon between statements.
Try a simpler case.
Try it OnVisible on an empty screen, and make a control on one of your other screens to navigate to it. Or even, do it on a button select instead on any screen and add a random button for testing that you plan to take out later.
Try a hard coded string as the Flow argument instead of another control's value. Try using a simple control (or set a variable) and see if you can update that rather then using a Collection (for now). Then perhaps try a variable for example. Then slowly change this gradually to Collection, get rid of your hard coded string, etc. and retest and work into your final scenario.

Was this reply helpful? Yes No
Arcr0s 16 on at

Like (0)

Report

Thanks for the reply,

However I need that second semicolon otherwise PowerApps cries because Notify is a new expression, they just act as a normal escape semicolon. This is not the issue, I have used this pratice in all my other apps and that has never been a problem.
Secondly there is nothing wrong with the parameters I am passing to Flow, both Flows I am using work 100%.
The pdf is created just fine and just as I designed it and the other Flow correctly checks for the file and returns the correct boolean. I have checked the Flow log which is again telling me everything is working just perfect, except it is not.

Edit:

I have tested it on Button press and other things but none of the work.

Was this reply helpful? Yes No