Announcements
No record found.
We are seeing issues with our migration of embedded canvas apps. When we migrate the Canvas App and the Model Driven Power App form, the form is retaining a Static App Id property that does not change to reflect the app in the current environment. IE when we import a solution with a Canvas App and a Form Customization referencing the app, the form in the target environment is still referencing the app that lives in the source environment.
What are the best practices when migrating an embedded canvas app? Should we be having to update a static id in every instance the customization is imported to?
Hi Tim,
It is recommended to post your issue to the forum of Power Apps for more help.
Best Regards,Nya
Hey Tim, hopefully you've figure this out already. According to the documentation, the App ID is unique in each environment, but the App Name is consistent. If you have the App Name filled out properly with the logical name of the app, then it will properly load the current environment's app after deploying to a new environment. This is confusing, because you'll still have the control configured with the App ID of the original environment, but the App Name will override that.
docs.microsoft.com/.../embedded-canvas-app-add-classic-designer
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Stars!
Thanks to all of our 2025 Community Spotlight stars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Tom_Gioielli 22 Super User 2026 Season 1
Suriyanarayanan V 22
Eugen Podkorytov 14
