cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Regular Visitor

PCF component not updating for canvas app

We are testing and implementing a pcf component for a canvas app and are experiencing problems when updating the component.

 

When we install the component for the first time, we are able to import it into our canvas app and use it. After this we save and publish the canvas app.

The problem occurs when we are updating the pcf component (we change the content displayed in our case). After we import the new version of the pcf component in our environment and open our app we still get the old version of the component in our app (it appears the component is cached in the app).

 

We have tried to do the following to try to update the component in the original app:

- Update version number of manifest, and solution version

- Remove the component, save and publish the app, reopen the app and import the pcf component

- Use of managed solutions (build as release)

 

None of the above did solve our issue, the old component is used every time. We also tested with a different browsers to exclude browser caching issues.

 

When we create a new canvas app and import and include the component, it will use the correct component version (until we update the component again).

 

Has someone experienced this issue before?

1 ACCEPTED SOLUTION

Accepted Solutions
Power Apps
Power Apps

This is a bug in current experimental preview and fix is in progress. We are adding the flow for control update.

As a workaround you can
1. Create a new app and insert control to get latest.
2. Rename the control and add it to the app

Because of canvas apps behaviour of persisting app image, we will support older PCF version in the app until maker updates. This is different from model apps where u get latest from CDS.

Sorry for inconvenience, bug is already prioritized and will be available soon.

Hemant


View solution in original post

5 REPLIES 5
Power Apps
Power Apps

This is a bug in current experimental preview and fix is in progress. We are adding the flow for control update.

As a workaround you can
1. Create a new app and insert control to get latest.
2. Rename the control and add it to the app

Because of canvas apps behaviour of persisting app image, we will support older PCF version in the app until maker updates. This is different from model apps where u get latest from CDS.

Sorry for inconvenience, bug is already prioritized and will be available soon.

Hemant


View solution in original post

How/where can we be notified when this is fixed?

Regular Visitor

Is this fixed? 

I have the same problem, I can see the post is more than 1 year old..

Yes this was addressed back then. Are you seeing this repro'ed . Please start  a new thread with detailed steps.  Please note that the control version needs to be updated in the control manifest to upload the newer control version on the server. Once that is done , reopening the app for editing should prompt maker about the newer control version available. 

 

Hemant 

Regular Visitor

I get the "Update Code Components" popup, I click on "Update" then a new popup appears saying "Error Opening File".

If I check the log in the browser console, I can see 'errorMessage"PowerApps control's template is not registered."'.

 

Any clue?

Helpful resources

Announcements
secondImage

Experience what’s next for Power Apps

Join us for an in-depth look at the new Power Apps features and capabilities at the free Microsoft Business Applications Launch Event.

Power Apps Community Call

Power Apps Community Call: February

Did you miss the call? Check out the Power Apps Community Call here.

New Power Super Users

Congratulations!

We are excited to announce the Power Apps Super Users!

New Badges

New Solution Badges!

Check out our new profile badges recognizing authored solutions!

Users online (16,500)