Announcements
Problem: Creating a new component with Input parameters. When using the component and setting the custom input parameter with a variable, the value passes thru, as the variable is reset, the control does not update with the variable. Replication Steps are recorded in the 2 min 20 sec recording showing the issue.https://www.pbeck.co.uk/2020/02/power-apps-component-potential-bug.htmlInitial Hypothesis: I have a large Power App project that uses this technique a lot. The global variable were working until Fri 14 Feb 2020. I believe the Power Apps version has been updated and is causing the issue. I have tried the work on multiple environments and tenants. It is happening across them all.
This is a known issue in the new release that should be fixed soon. As a quick fix, local variables - UpdateContext() - seem to be working correctly.
---If this answered your question, please click "Accept Solution". If this helped, please Thumbs Up.
I have been fighting this bug all morning! I am glad someone reported it and it will be fixed. I have a large project I am working on that I am due to preview tomorrow. This is a huge deal that doesn't take long to resolve (like today!).
Thanks Eric. Good to know MS are on the case. I can live with the work around.
Hi Paul - I am curious how are you implementing the workaround? Are you setting up context variables on each screen?
I have not tested it, but I saw on Twitter that collections are working too. You could add your global variable to a collection like this:
Collect(varCollection,{Name:varName,Value:varValue}
Then reference it like this
Lookup(varCollection,varName=MyVariableName).Value
Eric,
I would have liked to be informed about bugs like this instead of spending all morning trying to find out why suddenly all my components no longer correctly update..
Eric, Thanks for the tip, but this would take me too many hours to implement and test.
@Anonymous
The key takeaway for Microsoft and the Powerapps team here, is that if you discover a bug in the online tool, you roll back to the latest stable release immediately.
Containers are not really considered experimental, more like a key need for reusability. Just like functions (globally and locally defined), they are drastically needed to reduce code and avoid the Powerapps creator to become slow.
@jwillems
I would typically agree with you, but this is why components are off by default and you must go to Advanced Settings and turn them on under the 'Experimental Features' menu where it states they may change, break, or disappear at any time.
Microsoft PowerApps is on the edge of innovation and I tend to believe everyone here are still relatively early adopters. To innovate, you must breath things.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our community stars!
Expanding mentorship, skilling, and AI innovation
These are the community rock stars!
Stay up to date on forum activity by subscribing.
WarrenBelz 429 Most Valuable Professional
11manish 191 Super User 2026 Season 2
MS.Ragavendar 122 Super User 2026 Season 2
