cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
aaroh_bits
Resolver I
Resolver I

connection not configured for this service

Hi All,

 

Background Info

 

  • Using Power Apps and Power Automate with back end as Dataverse.
  • All Artefacts are under a Solution with maker.powerapps.com for ease to move to environments at later stage.   
  • We need to generate PDF via OneDrive (no premium connector)  and send email to end user when workflow completes.

What Works:

 

  • As flow owners for that workflow and has following connections

    aaroh_bits_0-1618457635286.png

     



  • Once workflow kicks in a success message in Power Apps is shown asaaroh_bits_6-1618457780193.png

     

  • Submit button action in Power Apps is as follows:

 

 

If(
   Not(IsSubmitError),
    IfError(
        PurchaseRequestApprovalSubmission.Run(Text(HelpDeskWorkflow)),
        UpdateContext({IsSubmitError: true});
        Notify(
            "The workflow was failed to start. Message: " & ErrorInfo.Message & "& Error Kind" & ErrorKind,
            Error
        ),
        UpdateContext({IsSubmitError: false})
    )
);

 

 

What does not work

Other non- flow owners do not trigger the workflow

 


  • User Alex as following connection and OneDrive connected for Alex’s account.
    aaroh_bits_2-1618457635295.png
  • But when I clicks on Submit  workflow, he gets this error

     

    aaroh_bits_3-1618457635296.png

  • Tried may other options such as
  • We removed the OneDrive action inside flow, then re-add back. Then updating the connection reference inside the app.
  • We ensured there’s no other dummy connection inside the flow. Then updating the connection reference inside the app.
  • We Deleted the OneDrive connection that connects to the flow, then re-add back. Then updating the connection reference inside the app.
  • We created another dummy app, trigger the workflow, then the error message shows up as: “HelpDeskWorkflow.Run failed: connection not configured for this service”.
  • We created another dummy app, create another dummy flow, both are outside the solution, the workflow triggers just fine.
  • We Exported the flow package (.zip), then import back to the environment.
  • With the imported flow package (.zip), we created another dummy app and trigger the workflow, it works as per normal again. The flow was imported outside the solution and can’t be added into the solution.

 

Stumbled into a quite a few of issues in the community forum

PowerApps Flow Error : "Connection not configured for this service", when its in included in the Managed Solution and deployed

https://powerusers.microsoft.com/t5/Building-Power-Apps/PowerApps-Flow-Error-quot-Connection-not-con...
My experience with connector/connection problems, and multiple connections to same connector  
https://powerusers.microsoft.com/t5/Connecting-To-Data/My-experience-with-connector-connection-probl...

Connection not configured for this service (with Microsoft Support ticket details )

https://powerusers.microsoft.com/t5/Building-Power-Apps/Connection-not-configured-for-this-service/m...

Any suggestions or pointer will be greatly appreciated.

@martinav @CFernandes  @jinivthakkar  @Pstork1  @v-xida-msft 

39 REPLIES 39

Hi

 

Check by going to the Powerapps datasource. Check the status of the flow connection. If it say Not Connected, remove and ADD the flow again. This will restore the connection.

well it is not connected. but the thing is i want the solution to be managed and not allow app configurations.

i tried several ways since the app and flow was not initially created in the solution but added later on.

I dont want to allow users in other tenants to customize.

Is there any other way?

Hi

 

If you don't give the rights, they won't be able to customize.
When I try exporting, every time one flow connection goes away and others remain intact. I don't have any idea why I'm having issue with that flow. Most of the solution provided in the community was to reconnect. So in order to do that , you need to export unmanaged solution. 

 

I'm sorry I was no help.

Thank you for your response!

There are several bugs that needs to be fixed in order for exporting solution to function properly.

These are known issues

Do i handle the rights from the new tenant? Since i dont have much experience with the admin center and user roles. Can i prevent that from my tenant?

Hi

 

When sharing the App with others, if you don't assign co-owners they cannot edit the app. I meant like that we can restrict customization. Hope that what you need

liridonuka
Frequent Visitor

What you actually missing here according to error message is assigning security role (Basic User and Flow RP - Role) to the users.

In my case I had a working canvas app with "Basic User" permission assigned to the user, and everything was working great.

Then I copied the solution to another environment so I could start deploying updates to the prod environment from a dev environment and even testing them in a test environment first. Well I got it all working (using all unmanaged solutions) after some trial and error, but at first after importing the new unmanaged solution and updating the existing solution in the prod environment, I was getting OP's same error for the first (and presumably all) flow(s) that would run inside the app.

Did importing a new version of the solution cause the "Basic User" permission to get overwritten? Since I had already created that permission, I went with the suggestion provided by @aaroh_bits but now I too am wondering what, if any, unwanted permissions I've just granted by doing so.

I believe I have the SharePoint site locked down where each list or file or library has the permissions required to keep private data private. I've previously gone through each SharePoint list and modified the permissions so users can only read and edit records they've personally created (and various other permissions like read-only but no edit or read and edit all, depending on the requirements of each list), and that works fine for that one SharePoint site, but what about other data and files? All I did was change "Process" to "Read". But I did notice a lot more green in my settings, compared to @aaroh_bits, makes me wonder if my settings are too broad to scale this up with privacy requirements intact.

So, at least in my use case, it did seem like more than just the existence of the "Basic User" security role...


@liridonuka wrote:

What you actually missing here according to error message is assigning security role (Basic User and Flow RP - Role) to the users.


Will I have to fix this same problem again every time I update the prod environment solution using an exported unmanaged solution from the dev environment?

EDIT: Update, I checked again just now and all three of my environments (dev, test, prod) all have the same (default?) settings as @aaroh_bits and "Read" permission is NOT set to "organization" but only "user"!!! I swear I changed this and saved it in the prod environment yesterday. I can't remember if I updated the solution again after that... but yeah it doesn't seem like the change I made to that setting actually matters? I'm so confused now.

HEATFreight
Super User
Super User

Everything is working for me now somehow with the default of Process>Read>User, but I swear to Sol I changed that setting yesterday! But it could be something that automatically gets updated by other processes or settings changes? Or something weird is going on. I also swear I saw a lot more green (high level permissions) in a lot more columns in that >Customization tab of the "Basic User" security role, but it's possible I was looking while the solution was still finishing import? Otherwise I can't explain why I remember seeing a ton of more permissive settings than I'm seeing now and why that particular Process>Read>Organization setting change didn't seem to take. I assume it just resets if you update the unmanaged solution ¯\_(ツ)_/¯

The issue with this is that fact that you PowerApp will no longer be Managed.  It essentially becomes unmanaged and any solution updates will not take in the PowerApps going forward.

I have never used a managed solution in my prod environment. Everything works fine.

I update prod solution by exporting dev solution unmanaged and importing into prod. Maybe one day I will switch to managed, but for now this is working for me. The prod environment is only used by two people currently, so this feels like the right way to go about it. Everything is much easier when unmanaged.

I did test a managed solution in my test environment and I didn't understand what was going on or how it was all supposed to work. So I stuck with unmanaged. Eventually it will probably be necessary to switch to managed, but currently I don't understand all the implications of managed vs. unmanaged. Always learning!

What I can say for sure is that the >Security Roles >Basic User >Process >Read >Organization setting did take for good this time. It seems to remain set to organization even after updating my solution, which makes sense because it's an environment level setting. Not sure why it disappeared after the first time I changed it. Changing the setting fixed the issue I was having, so it seems like the setting change worked. But then later I saw that it had reset back to default. Yet now the >Organization permission is persistent. Go figure.

Yeah, I was just trying to follow MS process.  Un-Managed for Dev,  Managed for Staging and Prod.   What you are doing is fine as long as it works for you.

 

Setting Security Roles >Basic User >Process >Read worked for me after I made sure my users were set as Basic Users.

 

Typical MS

KodyN
Frequent Visitor

Has this been solved for anyone yet? I have a similar issue.

Wanting to follow MS process and have Un-managed dev projects imported as a managed solution into a production environment. 

Currently this seems to break flow connections anywhere from outright not recognizing workflow id's to just spitting back "Connection not configured..."

This seems to have been a known issue for at least 2 years now. Anything yet?

HI

 

Did you check rights of the users for the SP list?

 

Also I found when exporting, if the flow owners is different from test and dev environment this happens.

 

KodyN
Frequent Visitor

The flow flat out doesn't run in general. I don't think that it has anything to do with SP but I will check. Only one flow connection fails every time no matter how I import or export(Same flow each time).

I looked at the canvas app flow connection using the default solution of the production environment and it says that the flow is not connected. Like mentioned before by others, I can't edit that without creating another unmanaged layer which defeats the point of having a managed solution in the first place.

KodyN
Frequent Visitor

Checked SP list and all the flow user is an owner. 

As for exporting flows and importing using the same owner for the connection, how can you do that if it's in a separate organization? Most of our projects will involve using our organization tenant to build the apps and follow this pattern:
development env > export managed > switch tenant > switch to prod env > import managed

How can that user exist in both tenants?

Your solution worked for me, thanks!

This worked for our organisation.  Many thanks for publishing this here. 

 

I have to admit though; I am confused why this subtle change is needed in the Basic User Role to carry this action out?

Also check the user is member of the environments users in the admin center.

Today is June 2022 and I have similar issue.

Users are working find last few weeks and suddenly some users fail to trigger flows from canvas app.

Perform the permission change for Process > Read > Organization and seems to be fixed.

 

Also when I exported an unmanaged solution and import to another environment (same tenant). I found that beside the owner (who imported the solution) everyone else including System Admin cannot associate the app with other workflows. The error is "Failed during http send request". 

 

I spent at least a week to understand how solution work and setup environment variables. End up it is just a buggy approach. It is really not a good choice. Solution only add 10 layers of complexity to your work.

Helpful resources

Announcements
Power Platform Conf 2022 768x460.jpg

Join us for Microsoft Power Platform Conference

The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.

May UG Leader Call Carousel 768x460.png

June User Group Leader Call

Join us on June 28 for our monthly User Group leader call!

MPA Virtual Workshop Carousel 768x460.png

Register for a Free Workshop

Learn to digitize and optimize business processes and connect all your applications to share data in real time.

Power Automate Designer Feedback_carousel.jpg

Help make Flow Design easier

Are you new to designing flows? What is your biggest struggle with Power Automate Designer? Help us make it more user friendly!

Top Solution Authors
Users online (1,085)