Service | Customer Service, Contact Center, Fie...

What are best practices for migrating an embedded Canvas App on a Model Driven Power App form?

(0) Share

Report

Posted on by TimTownsend

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?

All responses (2)

Answers (0)

Suggested answer

ChadAlt 367 User Group Leader on at

Like (0)

Report

RE: What are best practices for migrating an embedded Canvas App on a Model Driven Power App form?

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
Nya 29,056 on at

Like (1)

Report

RE: What are best practices for migrating an embedded Canvas App on a Model Driven Power App form?

Hi Tim,

It is recommended to post your issue to the forum of Power Apps for more help.

Best Regards,
Nya