Migrating a canvas app and flows as managed solution

(0) Share

Report

Posted on by psreek

323

Hi,

We have built a Canvas App that connects to SharePoint Lists and Document Libraries. The app also uses Power automate flows to update ACL, upload and delete files on SharePoint. This works fine in our development - the flows are called properly.

We have these added as an unmanaged solution in our dev environment -

We have then exported this solution as a managed solution and imported the same to our prod environment and updated the environment variables to use the production sharepoint site.

We have given access to end users to use this app. When the user opens the app, and clicks any button that invokes a power automate flow, the flow is not called but instead the user gets this error. The users are only added to the security group of the production environment. As no dataverse table is used, no security role has been assigned to the users.

But, if a System Administrator in the production environment opens the app and clicks buttons that invoke power automate flows, the flows are invoked without any issue.

Please let us know what is causing this.

Please note that both in the dev environment and production environment, the end user has only been added to the security group of the environment. No role has been given to the user in either environments. But, the app works fine in the unmanaged solution in dev but does not call the flows in the production env.

Categories:

Building Power Apps

All responses (11)

Answers (1)

Sort by

darylvogan 274 on at

Like
a
(0)

Report
Copy link

Link copied!

we add app opener and basic user role.
Jonathan Manrique 2,695 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @prathyoo

You must share the flows with the users, the best way to do this is through a security group, just as the application must be shared with the end users

Another thing to keep in mind if at any time you are using a premium trigger or action

If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
You can accept more than one post as a solution
psreek 323 on at

Like
a
(0)

Report
Copy link

Link copied!

@darylvogan Thanks. But it seems to work fine in the dev environment without adding the end user to any security role.
psreek 323 on at

Like
a
(0)

Report
Copy link

Link copied!

@Jmanriquerios -How do I share a flow with an end user? The only option I see is to make a user a co-owner of the flow. That is not a possibility for us. We will be sharing the app and associated flows with around 5000 plus users and they can never be allowed to be co-owners of the flow.
Jonathan Manrique 2,695 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @prathyoo

It is not being a co-owner, it is being able to run the application

If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
You can accept more than one post as a solution
psreek 323 on at

Like
a
(0)

Report
Copy link

Link copied!

@Jmanriquerios - Thanks, but you have shown a screenshot of sharing the app (while you had mentioned sharing flows in the first post of yours). That is something standard and I have shared the app with the end users. The user in question can open the app (because it is shared), but when they click any button in the app which is supposed to invoke a power automate flow, the flow is not invoked but the user gets an "error" on the screen.
psreek 323 on at

Like
a
(0)

Report
Copy link

Link copied!

Further -

The app shared in DEV ENV -

The App shared in PROD -

The user in DEV ENV where the APP and Flows work in the unmanaged solution -
The user in PROD where the App does not invoke the flows -
From what I can see, both the DEV and PROD have the user setup exactly the same. The only diff is that in DEV the App and Flows are in the unmanaged solution while in prod they are in the managed solution exported from dev.
Verified answer

psreek 323 on at

Like
a
(0)

Report
Copy link

Link copied!

And here is the fix that worked for me (pretty bad one for a managed solution).

In production, I opened the app for edit. Now this cannot be done via the managed solution but can be done via the Default Solution -

Next, once the app is opened, go to the list of flows tab -

Remove each of the flows using Remove from App

Now add the flows again -

After this publish the app. And now the new version of the app works fine and when end users click buttons that invoke the flows, the flows are actually invoked just like in the DEV environment.

Users were only added to the security group of the production environment. No additional security roles were given to end users. This will ensure that the user only has access to the app and not to anything else in the production environment.
Jonathan Manrique 2,695 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @prathyoo

What it keeps telling you is that it needs to be assigned a security role. If the users do not have the necessary permission it will fail.

You can validate if the sharepoint permissions are given to the users who are running the flows, because one of the characteristics of making flows in Canvas Apps is that they are executed with the user who runs the application. And in some flow the user does not have permission, and it occurs to me that it could be the Sharepoint list

If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
You can accept more than one post as a solution
psreek 323 on at

Like
a
(0)

Report
Copy link

Link copied!

We fixed the issue as described above. SharePoint permission is not the issue here. The issue was that on button click inside the canvas app, the flows were not invoked. If SharePoint permissions are the issue then the flow would have been called and the relevant SharePoint connector within the flow would have failed. Example -

All our flows use Service Accounts to run and we use the Run Only Users to ensure that SharePoint connectors use the Service Account and not the user opening the Canvas App.