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

Common Components from Component Libraries lose inputs on review of changes

I've been building Common Components inside the Component Library so that they can be easily used across Power Apps.

I sometimes go back to the Common Component to add more functionality after is has been imported into a Power App.

This includes adding new inputs and/or outputs. After changes, I then Save and Publish the Component Library.


What I have noticed, is that sometimes afterI have added new inputs, when I Review changes in a Power App and accept the udpate, the Common Component used throughout the App has not updated properly.

I have seen the new inputs come through, but it has then lost some of the old inputs, which should still be there.

And by lost, I mean that they are no longer available to be set.

In the Component Library, it is all fine, but not in my Power App.

Sometimes, I have used the component in many places, so I do not want to remove the component and reimport it.

It should just work and update properly.


In the example below, I added a new input called "Default Multi Selections".

After I update the component inthe Power App, I get the new "Default Multi Selections", but I have now lost "Default Selection".




Resolver I
Resolver I

Hello @BenGin,


I guess this is the normal behavior:  as you have edited the component in your Power Apps, a local copy has been created. This copy will not received the updates when you change the main component.


This is mentionned in documentation - Known Limitations:


  • If you import a component from a component library, you can't edit it inside the consuming app. If you select Edit component, you'll see an option to create a copy of the component inside the current app for you to make changes:


    If you select Create a copy, the component is copied to the local app. The local copy of the component appears under the Custom category in the Insert pane. This local copy of the component won't receive updates if a new version of the originating component library is published later.

@lcimon  I did not create a local copy in the Power App. I never edit it because I want to be able to make updates in the Component Library and be able to update.

So, I updated the Component Library.

Back in my Power App, it detected a change and I accepted the update. The new update Input parameter came through. But it lost an existing Input parameter that I did not delete from the Component Library.

Advocate II
Advocate II

Ok, so, Component Libraries are super buggy.


I can't believe that PowerApps has been around so long, but Component Libraries are in Preview and are super buggy.


In this particular case:

  1. Make an insignificant mod in the Component Library in the "Screens" tab (used for texting the component before publishing)
  2. Save and publish this (to force a new version that had NO changes to the component)
  3. Open PowerApp, review the change and accept

The problem with this method, is that now any other PowerApps that use this common component will show up as needing a Review, and if I update in those, I sometimes have problems that should not exist, and I end up in a vicous cycle going through the above steps.


I've also found in other cases where I update a Common Component from the Component Library, where upon update in a Power App, it can have strange appearance and behaviour. In these cases:

  1. Make your mods in the Component Library
  2. Save and publish
  3. Open PowerApp, review the change and accept
  4. Observe silly things happening with the component such as:
    1. Fill colour not reflecting the input parameter
    2. Size of the component completely wrong
    3. Missing Input parameters (as per the original post)
    4. Other weird and wonderful things that have no explanation at all
  5. Save and close the PowerApp (with the silly things)
  6. Open the PowerApp again
  7. Sometimes it is ok, but somtimes, I have to to rinse and repeat from step 4 again
  8. In the absolute worst-case where it just won't reflect how it is in the Component Library, I have had to delete the Component from the Power App and re-import


I come from a background programming in the R programming language with Shiny as the App presentation layer. In there, I have written packages with functions and Shiny Modules (where Shiny Modules are equivalent to Common Components) to make it easier for my team to utilise repetitive code and ensure some consistency in the apps we create. Hence, when I started in Power Apps and learnt about the Component Library, I jumped straight into creating Common Components for my team. I create them in the Component Library and build test cases in the Screens page that exists in the Component Library. But then, when my team mates (or myself) import these, they don't always work the same as in testing! Super buggy.

Resolver I
Resolver I

@BenGin, I'm also regularly facing issues with Reusable Component. 

A common issue is: components aren't properly rendered in the Power Appts Studio, but when app is opened as an end user, that work.


For your case, I suggest you to contact Microsoft to share with them your findings.

Advocate I
Advocate I

I've found a 'hacky' fix is to move the updated component in your app by dragging it, then clicking 'undo'. This causes PowerApps to crash, and when it comes back up, the component will be working again like magic.

Helpful resources


Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Top Solution Authors
Top Kudoed Authors
Users online (2,308)