Answered

Components - input parameters based on variables not working any more (bug?)

(2) Share

Report

Posted on by MrNappa

241

I have created some apps that rely on components to (for example) display stuff based on some input parameters. At some point in the last week (?) they stopped working properly (they were working fine before).

For example, I have a component that displays a text based on an input parameter "Text". On the form, the "Text" property of the component is set to "variable.name". But the label on the component that should display that value stays empty.

See attached example.

/edit: The example I attached only shows this with regard to displaying a text on a label in a component. But what makes this worse is that some of my components also have internal conditional logic to them based on boolean (or other) input variables. If that's not working, well that kind of breaks the whole app...

Categories:

Building Power Apps

Component test.msapp

I have the same question (0)

All responses (6)

Answers (1)

Safouene 14 on at

Like (1)

Report

Same problem here.
If you pass a variable parameter to the component and the variable value changes. The parameter becomes empty!!
Tested with a text, array, object parameters and always same buggy behavior.

I have a lot of components in different apps, fortunately it keeps working on the already published versions, i don't even dare to update them.

I've remarked also, if you pass this variable to a control on your app (let's say on the control text) and then pass to the component myControl.text, it keeps working. But we all know this is a very bad practice!

Hope Fixes this ASAP.

componentsproblem...

Was this reply helpful? Yes No
Safouene 14 on at

Like (2)

Report
Finally,
i've found a solution for this. Hope this helps if someone is facing the same problem
Origin: the problem is with Global variables; If a global variable is updated, the parameter becomes empty on the component
Solution: Instead of passing global variables, pass local variables
What i did, is on the 'Screen OnVisible' or the buttons 'OnSelect' as last Line, i've set UpdateContext( { locMyVariable: GlbMyVariable } )
In the component instead of passing GlbMyVariable, i pass locMyVariable
if you have a lot a variable parameters to pass to the component(s), you can all the updatecontext under a concurrent function
The parameters on the component should raise component reset
Frankly, i hope MS will fix this, so we can pass Global variables as parameters to the components. In more, there is now the Component library, so if i'm going to publish some components to be used by the 'Citizen developers', i'm not sure if they will understand / like the fact that they should use local variables each time instead of using the same variable everywhere.

Was this reply helpful? Yes No
Community Power Pla... on at

Like (2)

Report

Please refer to: https://powerusers.microsoft.com/t5/Building-Power-Apps/Power-App-Components-not-working-with-Global-variables-used-with/m-p/473414#M142132

Known bug

Was this reply helpful? Yes No
Verified answer

Mr-Dang-MSFT on at

Like (2)

Report

Hi @MrNappa @Safouene @Anonymous ,

A fix was rolled out earlier today for the issue involving components and global variables. Can you let me know if it has resolved the issue for you?

Was this reply helpful? Yes No
MrNappa 241 on at

Like (0)

Report

So far, it looks like it's working again. Thanks!

Was this reply helpful? Yes No
Safouene 14 on at

Like (0)

Report

Hello,

Yes, it's working!

Thanks for the quick and great support.

Was this reply helpful? Yes No