[ALM Accelerator - BUG]: Canvas App Share step is using canvasappid instead of uniquecanvasappid and fails to share app

[BJHF-power]

Describe the issue

In the Share Canvas App with AAD Group step of Build & Deploy pipeline, the pipeline attempts to share Canvas Apps with AAD IDs as provided in the User Deployment Settings. It does this using the canvasappid attribute of the app:

However, this fails with the error message attached, as the app ID that it attempts to share is associated to a different environment (in our case, the Production environment).

The canvasappid value is static; it doesn't change as the solution is moved between environments, and thus using it for the sharing step can cause failures. Instead, the sharing step should use the uniquecanvasappid, which is environment-specific as the solution is moved between environments, and which matches the app ID as displayed in the UI and as retrieved by Get-AdminPowerApp cmdlet:

Expected Behavior

The Canvas app share step should use the uniquecanvasappid attribute which holds the valid app ID in the target environment.

What component are you experiencing the issue with?

ALM Accelerator Pipelines

What solution version are you using?

May release

Steps To Reproduce

1. Create a new target environment
2. do a minimal copy of the old environment into the new environment
3. attempt to deploy a solution containing a canvas app into the new environment after the copy is complete

Anything else?

No response

[mikefactorial]

This will be included in the July release via microsoft/coe-alm-accelerator-templates#306

[CoEStarterKitBot]

@BJHF-power This has been fixed in the latest release. Please install the latest version of the toolkit following the instructions for installing updates. Note that if you do not remove the unmanaged layers as described there you will not receive updates from us.