Power Apps

Code component not updated with solution (The code component has been added in an App solution)

(0) Share

Report

Posted on by HCLin

124

Hi,

Our team is trying to use the Solution for version control of different environments.

In the App solution, it includes a custom control which is a code component.

(*The code component is not a solution itself, it has been added into the App solution)

(*Let's say we have environment env-1, and environment env-2)

But while we modified the code component in env-1 and exported it to env-2, everything in the solution in env-2 will be updated but not the Customer control, the Customer control will still be the old version.

I know it might work if we totally remove the customer control in env-2 first, then import the solution, but is there any way I don't need to go through this process every time that I would like to import a new version?

Thanks in advance!

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (3)

Answers (0)

Sort by

ryanspain 102 on at

Like (2)

Report
Copy link

Link copied!

Hey @HCLin,

When building the PCF control, are you ensuring that the version in the controls manifest is updated?

While the solution version might be increased when exporting your app solution from env-1 to env-2, your PCF control version will not. Changes will only be visible in env-2 if a newer control is imported.

See the below example for where the version is located in the manifest in source control. The version is on the 'control' element of the manifest XML file.

https://docs.microsoft.com/en-us/powerapps/developer/component-framework/manifest-schema-reference/manifest#example

Edit: I just remembered that I wrote some PowerShell to increment the control version in the manifest. See step 6 of Adding build tasks in my post here.

Hope this help!

Was this reply helpful? Yes No
Diana Birkelbach 3,072 Most Valuable Professional on at

Like (2)

Report
Copy link

Link copied!

Hi @HCLin ,

There are a few aspects which can play a role. Besides manifest incrementation, as @ryanspain mentioned,there might be important if you increment the major part of the version. In that case you would need to increment also the solution version. You can also have a look to the solution layers, because you might see a managed and an unmanaged version of the PCF in your environment at the same time. Please have a look to my blog, when I talk about this problems: https://dianabirkelbach.wordpress.com/2020/12/23/all-about-pcf-versioning/

Hope this helps!

Kind regards,

Diana

PS: Regarding PCFs deployment through solutions generated in an environment, you need to take care the use a minimized version of the control. But that's another question.

Was this reply helpful? Yes No
Suggested answer

abm abm 32,985 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi

Yes, it’s most likely a versioning issue. @ryanspain mentioned updating the manifest XML version, which should solve it. I encountered the exact same problem recently; once I bumped the version and recompiled the package, the deployment to Test went smoothly

Was this reply helpful? Yes No