according to this doc https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/share-embedded-canvas-app this is what supported way of moving Embedded Canvas App
"Embedded canvas apps are also solution aware. By default embedded canvas apps are created in the same solution as the host model-driven form. To move the embedded canvas app from one environment to another export and import embedded canvas apps as a part of a solution just like any other component."
Just want to ensure I understand this correct,
1. So if I have an embedded canvas app on the Case Interactive experience form which is the form that has been used in the model driven app "Customer Service Hub", let's say the solution hosting that form is called "Core". Do I export the import the solution that is hosting the "Core" to the target envrionment? or?
2. Will it work if I save the Canvas PowerApp locally and then import the msapp file to the target envrionment. Finally manually add the app id in the relevant form where I want to embed?
Or do you have an even better suggestion?
Many thanks in advanced
Xun
Solved! Go to Solution.
Hi,
Both options works however, in the latter we should also make sure app is shared with correct users to keep it visible. (because it is as good as creating new app in target environment).
If this answers your question, mark it as verified.
Regards,
Pavan Kumar Garlapati
Hi @xyd ,
Based on the two solutions that you provided, I think both of them works well.
I think the first solution would be better than the second one. If you save your canvas app as a local .msapp file, and then import it into your Target Environment, you need to save it into your Target Environment manually, and re-share this app to your end users again.
In addition, there are also some known limits with Solutions you need to know in PowerApps, please check the following article:
Best regards,
Hi,
Both options works however, in the latter we should also make sure app is shared with correct users to keep it visible. (because it is as good as creating new app in target environment).
If this answers your question, mark it as verified.
Regards,
Pavan Kumar Garlapati
Hi @xyd ,
Based on the two solutions that you provided, I think both of them works well.
I think the first solution would be better than the second one. If you save your canvas app as a local .msapp file, and then import it into your Target Environment, you need to save it into your Target Environment manually, and re-share this app to your end users again.
In addition, there are also some known limits with Solutions you need to know in PowerApps, please check the following article:
Best regards,
Ok it's good to know it is possible with both approach.
Just correct myself, with the 2nd option (import the powerapp package into the target envrionment) will require a zip file. at the least at the Preview stage for Import package, it will not except a the msapp file ...
So exprt the app and then import the zip file to another environment just work for me.
One thing I haven't try is to re embedded it to the relevant D365 form... but then that is why that import the Canvas App in as part of the D365 solution would be a better choice...
Yes, However double check when we import solution is it mapping to the correct canvas app id in the form control. when that verification succeeds then you are good to go.
Please mark it as verified if it answers your question.
Regards,
Pavan Kumar Garlapati
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
This training provides practical hands-on experience in creating Power Apps solutions in a full-day of instructor-led App creation workshop.
User | Count |
---|---|
181 | |
46 | |
46 | |
34 | |
33 |
User | Count |
---|---|
259 | |
87 | |
79 | |
68 | |
67 |