How to make the Canvas App id constant across environments?

[MadhanSA]

Hi,

I have an embedded canvas app in my development environment. When I export this app as a package and import it in my test environment, the App ID is getting changed. Because of this, I need to manually change the App ID in the form where I am using it. Is there any way to export the app with the same ID?

Thanks,

Madhan

[WarrenBelz]

Hi @MadhanSA ,

The whole idea of an App ID is that it is unique.

So exporting still leaves the original with the number. If the exported apps (or apps) had the same number, the system would have no idea which one to launch,

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

[MadhanSA]

Hi @WarrenBelz,

I agree. But I am not going to import the app in the same environment. The App ID will still be unique in the new environment.

[v-xida-msft]

Hi @MadhanSA ,

Actually, when you import a canvas app from one Environment to another one, it would create a new canvas app in your Target Environment rather than just copy/move the original canvas app into your Target Environment.

So the App Id value of the import app in your Target Environment would be different from that in your Source Environment. If you want to make the App Id constant during the importing process, I afraid that there is no way to achieve your needs in PowerApps currently.

If you would like this feature to be added in PowerApps, please submit an idea to PowerApps Ideas Forum:

https://powerusers.microsoft.com/t5/Power-Apps-Ideas/idb-p/PowerAppsIdeas

Note: In order to distinguish which Environment this canvas app is from, the App Id value within different Environment would be unique.

Best regards,

[spence_ac_]

Hi,

Does anybody know how to make it not a constant? For some reason when I try and deploy to a different environment within the tenant the app id stays the same so any changes I make in one environment affects the other.

Thanks

Spencer

[EricRegnier]

Hi @spence_ac_, @MadhanSA,

Not sure if you found a solution for this yet, but the resolution is to set the App Name in the embedded canvas app control properties of the model-driven form. When an App Name is present is takes precedence over the App ID hence you won't need to change anything after a solution import.

Hope this helps!

[BishopTecConsul]

Thanks for this tip, Eric. Unfortunately, that solution is not working for us. Now the embedded app is pulling from a different environment and performing functions on another CDSs data 😞

I'll have to start a Support ticket I guess

[EricRegnier]

Hi @BishopTecConsul, then your issue is not because of the App ID. It sounds like you haven't updated your connector/data source in the other environments. Still still point to your origination CDS/Dataverse. 

[BishopTecConsul]

Wish it were so easy. I have a copy of the canvas app in multiple environments in the same tenant. All connections are up to date and turned on after solution import. Strangely, it’s not the originating sandbox that it is still connected to, but one of other environment in the tenant.

[BishopTecConsul]

Sounds like it's a known issue. Importing into an existing environment doesn't give the Canvas app a unique ID.
I continue to work with MS on the issue.