Relaying way for deploying Canvas CustomControl (new version)

(0) Share

Report

Posted on by FlorianGrimm

Hi all

I'm struggle updating a new version of my custom control in the canvas app.

Does some body have a relying way of updating the custom control.

in the most cases I get an old version within the canvas app.

my current steps: remove custom control within canvas app; close canvas app studio; msbuild ; import new version; import custom control within canvas app studio, sometimes it works.

But I hope you know a relay-able way.

txs Flori

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (3)

Answers (0)

Hemant Gaur on at

Like (0)

Report
Copy link

Link copied!

Please ensure that the control version is updated in the manifest which is used by the canvas app to check for updated version. Canvas app should prompt when reopened if there is a newer control version on server.

Please let me know if the issue persist , Share the session ID for troubleshooting.

hemant

Was this reply helpful? Yes No
FlorianGrimm 21 on at

Like (0)

Report
Copy link

Link copied!

After trying again I noticed the version solution was updated but not the custom control.
Also in PowerApps -> Solutions -> My Solution -> Control
the Modified tells me 4 h ago.

in the \src\Other\Solution.xml
<SolutionManifest>
change <Version>1.2</Version> to <Version>1.3</Version>

in the ControlManifest.Input.xml
<manifest>
changed <control .... version="0.0.1" to <control .... version="1.3.2"

This worked:
I deleted the control and than the solution and import the solution.
Now Studio asked me to update the version.

I'll guess I should give pac pcf push a try...

txs flori

Was this reply helpful? Yes No
JP-09110045-0 on at

Like (1)

Report
Copy link

Link copied!

I'm coming in on this thread a bit late, but I do have a few notes on your comments.

1. When updating a control, you only need to update the ControlManifest.input.xml version, the solution version can stay the same.

2. Updating the major version of the control (in your case you changed from 0 to 1) isn't supported and that control will be skipped. Technically, the import should be failing with a message that major version can't be updated.

3. While 'pac pcf push' will work, you still need to update the ControlManifest.Input.xml version beforehand for canvas so that the canvas code can detect that the control has been updated on app open. This isn't an issue with model as it will always load the control from CDS, but for a canvas app with the stored control the version needs to be different then it was in the msapp file to see that there is an update.

Was this reply helpful? Yes No