Power Automate Flow triggered from Canvas App failing to run - Connection not configured for this service.

(0) Share

Report

Posted on by PhilB

I have simplified my problem to be somehow connected to the set up of the environment (I think)

I have a very simple single page Canvas App. It has a button the triggers a power automate flow.

The flow is very simple and returns a random number.

I have created this all within a solution and I export the solution and then import it into a test environment. (This happens whether am dealing with a managed or unmanaged solution).

If I share the app with a very simple user. The app works (ie a simple label generates a random number) - but the other label that is will be triggered by the button and calls the flow to get a random number won't work.

The flow.run fails with Connection not configured for this service

Oddly if the original version is shared with the same user it is able to work correctly.

So I have been looking for a means of ensuring that the instant flow is able to be 'enabled' for the simple user.

Any help or pointers would be greatly appreciated.

many thanks

Categories:

Building Power Apps

All responses (8)

Answers (0)

Sort by

v-xiaochen-msft Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @PhilB ,

You need to add a security role to the user who uses this app .

I assume you assign a basic user security role to the user. Then you need to customize the security role.

Edit basic User- > Customization -> Process (Organization/Green)

Best Regards,

Wearsky
PhilB 32 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi and Thank you for responding.

I feel that I'm missing something here.

The App and Flow that I have created was imported into the test environment. It was then shared with the basic test user (from within the solution, by selecting share for the canvas app). And the app is able to run - however, it tries to call a very simple flow - that is just returning a string.

Looking at the environment - that user is not listed. Environment -> Test > Settings > Users
Though that appears to be required for access to the environments data - which is not required (in this example).

I think what is confusing me - is that I have managed to share the app. It runs so the user has permission, but the flow is not connected/permitted. The user is a regular user, with licenses of Power Automate Free and P2. Since the App is 'standard' I would have expected it to be okay. Obviously, I missing some checkbox and can not find any clues from the system.
v-xiaochen-msft Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @PhilB ,

Please try adding a security role and modifying Process permission.

Best Regards,

Wearsky
PhilB 32 on at

Like
a
(0)

Report
Copy link

Link copied!

I appreciate that you feel this is to do with the security roles, but I think you may have missed the part I am not understanding.
In the original dev version in our dev environment - if I share the app the the test basic user the flow is able to be called and works. In that environment the test user is not listed in the settings under users.
When I import that exported solution - then shared to the same user and that version is run - the app runs, but the button to trigger the flow says the service is not configured. Like the dev environment the test base user is not listsed in settings -> users.
So in neither case are we dealing with the security roles , as far as I can see.

I just thought of something while writing this.
I wrote the simple canvas app and flow directly into the test environment (with the import user - not the regular developer user) and shared the app with the basic test user. It worked correctly.

So I'm still veering away from security roles. But think that my query now asks
Why would an imported solution (by a different user) - not import the required configuration/permissions for the functionality to work. Especially when this is the most basic version of a canvas app and flow ?
v-xiaochen-msft Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @PhilB ,

Just like accessing data in the dataverse, triggering a flow in the canvas in the target environment also requires some permissions from the security role. This is my guess.

Actually, at my knowledge , there is no microsoft documentation explaining this.

Many people had the same problem and submitted a support ticket. The solution above is the reply, and it does work...

Best Regards,

Wearsky
PhilB 32 on at

Like
a
(0)

Report
Copy link

Link copied!

Thank you again @v-xiaochen-msft . I have not been able to fully test that, until I can reach one of my colleagues.

I have looked but I can not find either other posts connected to it or the support ticket. Do you have links for these ?

It does seem an odd issue. That somehow the flows need to be connected to the owner of the app. Hence the issue seems to manifest itself only when the solution is imported as a different user.
I was able to correct the issue - if I have an unmanaged solution and remove the power automate flows and then simply re-add them.

It was also interesting to see the options around the Basic User security settings. On the customization tab - at the bottom it actually mentions in Miscellaneous Privileges Run Flows - which has organizational permissions.

One last query - when you mentioned the customization and the process table - you were on about give organisation privilage to the for Read ?

*** I've managed to find a work around.
I noticed the other day, frustratingly, that it is possible to still amended an app that has been imported in a managed solution - by looking at the Apps option and not through the Solutions. Which was not as expected.
But that does mean that I am able to edit the canvas app and remove and re-add flows and ... hey presto.
they work as I'd hoped.
v-xiaochen-msft Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @PhilB ，

Please take a look at this.

https://powerusers.microsoft.com/t5/Building-Power-Apps/PowerApps-Flow-Error-quot-Connection-not-configured-for-this/td-p/723401

Best Regards,

Wearsky
PhilB 32 on at

Like
a
(0)

Report
Copy link

Link copied!

Thank you for your help, I'm hoping that in the new wave of improvements this might get looked at - though it may not be an issue for enough users.