Issue updating a Canvas Application within a Managed solution

[RemiChambard2]

Hi,

I've a strange behavior that I can't explain myself relating to the update of a Canvas application from a Managed Solution.

To give you a little bit of context, I built my solution in a Community Environment on my Tenant. This solution contains multiple Dataverse tables, Power Automate flows and Canvas applications.

In order to deploy the solution in my customer Tenant, I export it as Managed and import it into his environment.

After updating the solution, I can't see the updates on my Canvas application. The application reflects the updates from the previous version. I also can see that the application was last updated the date and time the solution was updated.

However, when I export the application in a MSAPP file and look into its "source code", I can see all my changes.

I suspected it to be related to solution layers. However if I'm using the default import solution process, everything should be working fine.

I looked into the "Manage Solution Layers" screen for my Canvas app and here is what I see :

What is this "Active" solution as I've never made any updates to my application outside updating my solution ? Is it related to the new "Environment variable" feature as I've activated them in my application ?

I believe that I will not use solutions to deploy Power Automate flows and Canvas applications as it seems quite note working well for now.

Thanks for your time and help !

[RemiChambard2]

Hi,

Here are additional informations regarding my issue :

I have removed my solution and imported a new one. My solution uses at least one Canvas application with connection references to SharePoint lists and Dataverse tables. 

When I update the solution, my application is not updated with the one in the solution. It is still the previous version.

When I look into the application solution layers page for my Canvas application, it says that there is another layer on top the one of the solution (see screenshot in my first post). However, I didn't make any customization on my application outside the solution. So, this layer shouldn't exist as far as I know.

I'm wondering if using connection references sorts of create a new unmanaged solution layer when I import and sets the connections.

By the way, I also use Environment variables to update the URL of my SharePoint site and Lists id.

Any ideas ?

Thanks.

[joe_hannes_col]

Hello @RemiChambard2,

Just to clarify: do you see the solution layers in your target or your development environment?

Do you trigger your flows from your canvas app?

[RemiChambard2]

Hi @joe_hannes_col ,

I see them on my target environment. For now, flows are triggered based on events from a SharePoint list or Dataverse table. Not directly from an application.

Thanks.

[joe_hannes_col · Accepted solution]

Hello @RemiChambard2,

If you have not done any customizations in the target environment, and if you have not linked the canvas app to your flows it should be save to delete the unmanaged layer.

Have you tried deleting the second (upper) layer from your target environment? You may have to switch your user interface to English to do this:

I'm using German as another language, and as long as the UI is in English, I cannot delete unmanaged layers - please don't ask me why 🙂

[RemiChambard2]

Incredible / Insane ! :). I'm able to remove the Unmanaged layer switching to English. 

However, it doesn't explain why this unmanaged layer is there ... 😞

Thanks very much @joe_hannes_col  !

[joe_hannes_col]

I could imagine that the platform creates an additional layer once you make any changes to your app, even if you would not consider them customizations. E.g. connecting to a flow in your target environment (hence my earlier question). I'm not quite sure if an unmanaged layer is created when you're connecting your app to a different SharePoint site in your target environment compared to your dev environment, for example.

I had a look at a solution that is based on Dataverse only, and no new layer was created for the canvas app when I imported it into our production environment.

But you do (theoretically) have the option to compare the two layers.

Out of curiosity, have you tried that?

[RemiChambard2]

Hi @joe_hannes_col,

I'll perform additional testings next week as if it's proven on my side, there is maybe a cons for now using solutions with canvas application as when you update Connection references within a solution, it may "customize" the app and creates an unmanaged layer.

I'll try and let you know.

Thanks again @joe_hannes_col 

[RemiChambard2 · Accepted solution]

I finaly got it !!! 

My issue is due to the fact that I activate the "Auto assign per app passes" setting on my application in my target environment. When I activate this setting, it creates a new unmanaged layer. 

For me, it's quite a strange behavior as it shouldn't be something carried by the solution but a specific configuration for the app on a specific environment. Moreover, as I don't have any "Per app" licence on my DEV environment, I cannot activate it on my DEV to make it "transportable" to another environment

Any advise ? Is it something that will be adressed in the future as it's kind of a show-stopper using Canvas application with Premium connectors and solutions ?

Thanks