You’re offline. This is a read only version of the page.
Hi,
Does anyone have a workflow for updating and publishing new version of a control?
It seems to be quite cumbersome and there is a lot of room for error from what I have found.
So, how do you publish a new version of a control to an environment?
I removed the control from the app, delete the control from the solution and then deleted the solution.
My workaround has been to rename the the control, i.e. create a new control with a new name and publish that.
Is there not a simpler way? My controls are ending up with weird names and it seems to be a little bit complicated having to go through the process of creating a new control in order to update an exisiting one.
Br,
Jens
I am guessing that the control namespace or version might have been affected either by the latest publisher update or some intermittent version bump in manifest. Can you check the these details in the name and version of the control in the application page. Easiest way to get out of this is to unconfigure the control and delete the component\solution and then publish again (with optional version reset). Control version bump drives the control upgrade and this is fundamental way the controls are updated in production so this should help elliminate your immediate concern, let me know.
Thanks,
Hemant
Thanks @ScottDurow for the pointers. Will look into those when I have more time 🙂
For now, my headache is that my control don't seem to update in my environment when incrementing the version in the manifest and using msbuild to build the solution and then publish it manually.
I might not be doing it correctly which is why I am curious how others manage the publish workflow.
What specific part do you find cumbersome?
If you are talking about deploying as part of ALM - have you seen - https://powerapps.microsoft.com/en-us/blog/automate-your-application-lifecycle-management-alm-with-powerapps-build-tools-preview/
If you are talking about local development then you will need to msbuild the solution and deploy with the control version incremented - and then publish - you can't use pac push if the control version has incremented.
However, if you don't need to update the manifest you can use fiddler redirects to point bundle.js to a local version that is built constantly using
npm start watch
#1
WarrenBelz
85
Most Valuable Professional
#2
Michael E. Gernaey
57
Super User 2025 Season 1
#3
mmbr1606
55
Super User 2025 Season 1
Share
Report
All responses (
Answers (
