[BUG ?] Activating "Pass assignment" on a Canvas application creates an Unmanaged layer

(0) Share

Report

Posted on by RemiChambard2

166

Hi,

I don't know if it's a bug or an expected feature but for me it's kind of a strange behavior :

I have a Canvas application part of a Solution. This Canvas application uses Dataverse. On my customer environment, I have to activate the "Pass assignment" on this application to allow users to access it.

After I deploy my solution (in a Managed state) on my target environment, everything is ok. However, as soon as I activate the "Pass assignment" setting on my app, it creates a "Unmanaged layer" for that app (I can see it in the "View solution layers" interface for that app).

If I remove the unmanaged layer, the "Pass asignment" setting is still activated (which is good news :)).

For me, activating this setting should NOT "break" the solution layer and therefor not create an Unmanaged layer.

Thanks

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (0)

Sort by

EricRegnier 8,720 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @RemiChambard2,

Any customizations/configuration on a managed solution component (e.g. canvas app) creates an unmanage layer, this is by design. What's weird is the pass assignment doesn't switch to off after removing the umanaged layer. Did you try set it to "on" in your source (ie dev) environment to import as "on" by default?

Cheers

Was this reply helpful? Yes No
RemiChambard2 166 on at

Like (0)

Report
Copy link

Link copied!

Hi @EricRegnier

In fact, it was what I was expecting when I removed the unmanaged layer. However the setting is still activated. And I can't activate it on my DEV environment as I don't have any "Per app plan" licence on my DEV Tenant (so the option is grayed out).

There is definitely something strange / wrong about it as :

- The setting should have been set to false after removing the unmanaged layer (which hasn't, but that's fine for me :))
- As far as I'm concerned, activating that setting shouldn't "break" the layering system as in a DEV environment, I don't think it's common to have "Per app" licences. For me, it's more of an environment setting.

Strange isn't it ?

Was this reply helpful? Yes No
EricRegnier 8,720 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Typically the dev environment is in the same tenant as prod so this usually won't be an issue from a licensing perspective (FYI since your organisation has multiple tenants, it can incur more/duplicate licensing costs). Maybe have a temporary Per app plan license in your dev tenant to configure that setting and then remove that license? This could probably solve your issue.

Also, you can contact Microsot support at https://admin.powerplatform.microsoft.com/support to report that unexpected behavior when remove the unmanaged layer. Keep us posted 🙂 But for "activating that setting" this is as designed and is expected to create a new unamnaged layer on that app, so I wouldn't consider this is unexpected behavior.

Cheers!

Was this reply helpful? Yes No