Showing results for 
Search instead for 
Did you mean: 
Advocate I
Advocate I

Power App Components not working with Global variables used with Input properties

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.

Initial 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.


Accepted Solutions
Not applicable

The issue is resolved - Microsoft has released a new Power Apps build version today 3.20022.17 and the issue is 100% resolved 🙂

View solution in original post

Hi @JroderickMP @paulbeck1 @jwillems ,

A fix had gone out earlier today. Can you let us know if the issue is resolved for you?

View solution in original post

There was a problem with the rollout to, so if you are seeing version 3.20022.19, it may not work yet. The rollout to preview should be complete later today. Apologies for the inconvenience.

View solution in original post

Resident Rockstar
Resident Rockstar

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:




Then reference it like this





Not applicable



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.

I suggest keeping an eye on the #PowerApps feed on Twitter for immediate awareness and then check the service health center to see if Microsoft is aware of the situation.
The main takeaway here is to be very cautious about using experimental features in production apps.



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. 


Helpful resources

Power Platform Call June 2022 768x460.png

Power Platform Community Call

Join us for the next call on August 17, 2022 at 8am PDT.

Power Platform Conf 2022 768x460.jpg

Join us for Microsoft Power Platform Conference

The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.

Users online (2,211)