cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
GLMSDev
Level: Powered On

Update Component

Hi,

 

I have worked on the component and created the app. Now, when I have changed my code and used following commenad..

 

1. MsBuild /t:restore

2. Msbulid

 

it generates the zip file. Now, I already have component uploaded. first it does not ask if i want to replace the component. and second new code does not take effect. 

 

How do i make sure that my code is updated and running in the model driven app ?

1 ACCEPTED SOLUTION

Accepted Solutions
Power Apps Staff HemantG
Power Apps Staff

Re: Update Component

It is following attribute in manifest. 

<control namespace="MyNamespace" constructor="MyControl" version="0.0.1" ...
 
Note that if there are incompatable changes in the control manifest like say removal/addition of the required property than the import fails. This is because there is no way for the current version configuration to account for the change. For these rare cases, please remove the control from configuration and then uninstall it. 
 
 
 

View solution in original post

6 REPLIES 6
Power Apps Staff HemantG
Power Apps Staff

Re: Update Component

You would need to update the control version in the manifest file. We are working on improving the user experience here as multiple folks have reported this.

There is no override warning as the action of solution import with the updated control version implies the upgrade intent, like all other solution components.
GLMSDev
Level: Powered On

Re: Update Component

Can you please provide which tag in manifest file ? When I did it threw an error of version not matching and  did not allow me to upload the component.

Power Apps Staff HemantG
Power Apps Staff

Re: Update Component

It is following attribute in manifest. 

<control namespace="MyNamespace" constructor="MyControl" version="0.0.1" ...
 
Note that if there are incompatable changes in the control manifest like say removal/addition of the required property than the import fails. This is because there is no way for the current version configuration to account for the change. For these rare cases, please remove the control from configuration and then uninstall it. 
 
 
 

View solution in original post

Highlighted
mcutchins
Level: Powered On

Re: Update Component

I tried changing the version number and the changes still did not take.  I have to remove the solution (which entails removing the control from each field, form, view, etc. it is associated with) and then import the solution as new.  This is not great from a maintenance perspective as manual changes are tedious and error prone. 

Anonymous
Not applicable

Re: Update Component

@mcutchins This was helpful for me.  I accidentally posted the same topic as you.  This definitely is a lot to just update the component after you make changes to it.

Power Apps Staff GregHurlmanMSFT
Power Apps Staff

Re: Update Component

If you update your control version *and* the solution version, you should see an update without having to delete the old one first. We recognize this isn't ideal, and are working on a better devloop-deployment story.

Helpful resources

Announcements
thirdimage

Power Apps Super User Class of 2020

Check it out!

thirdimage

New Badges

Check it out!

thirdimage

Power Apps Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

sixthImage

Power Platform World Tour

Find out where you can attend!

Power Platform 2019 release wave 2 plan

Power Platform 2019 release wave 2 plan

Features releasing from October 2019 through March 2020

SecondImage

Difinity Conference

The largest Power BI, Power Platform, and Data conference in New Zealand

Users online (4,531)