connection not configured for this service

[aaroh_bits]

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
  
  
  
  
• Once workflow kicks in a success message in Power Apps is shown as
• 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.
  
• But when I clicks on Submit  workflow, he gets this error
  
  
• 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 

[abhishekgawde]

I am also facing the same issue.

But for me the flows are triggering in the development environment for both the owners and non-owners.

However, the flow does not get triggered after the solution was exported and imported into the production environment. I used the Monitor functionality to check the issue. Here is the error message i receive.

The Run-Success was for the owner, whereas it failed for the non-owner.

@yashag2255 can you please help or provide some hints/ guidance. Thank you 🙂

[aaroh_bits]

Thanks @abhishekgawde for your message and I guess we are in same boat.  

[yashag2255]

Hi @abhishekgawde / @aaroh_bits 

I have seen this issue as well while working with flows associated with canvas apps and then exported as a managed solution and imported in another environment. The main issue is that the flow and app connection gets broken (at least that is what I have seen) and based on a recent update from MS this was fixed (but I confirm that I still see the issue). 

How I resolved it: 

In the environment, where you have the managed solution, go to the default solution of that environment and you should be able to see the flow associated to the app over there. Open it in edit mode and it may ask you to fix some of the connections. Once you do that, you should re add the flow in the canvas app and then it seems to be working as expected. 

Hope this Helps!

 If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[abhishekgawde]

Hello Yash, thank you for the recommendation. However, it did not resolve the issue.

I just created a new solution with just one canvas app with a button. The button triggers a flow. The flow simply sends an email using the Mail connector to me. I exported it as managed and then imported in the production environment. I faced the same issue. I tried following the steps @yashag2255 mentioned, but there were no broken connections in the flow. 

Has it got anything to do with recent updates or the release wave 1, 2021?

@CST @DamoBird365 @Mira_Ghaly @KrishnaV 

[SCTdan]

My thread on the issue- https://powerusers.microsoft.com/t5/Building-Power-Apps/Connection-not-configured-for-this-service/t...

What powerapps version and authoring version does it show you on, and is it different in your dev vs prod environment?

I did a similar test, solution with one powerapp that consisted of a single button, tied to a flow that only had a compose action.  No connections in use aside from Logic Apps when sharing the app.  Same issue.

[abhishekgawde]

The Power Apps version is the same in both the environments 3.21035.34

I was able to resolve the issue with a work around. Basically, in the production environment remove the flow connections from the Data Sources in the  Canvas App and then added it again. However, this creates unmanaged customizations in the Canvas App component. This essentially restricts me from making any future upgrades to the app, as currently RemoveActiveCustomizations is not supported for components of type CanvasApp.

[abhishekgawde]

The authoring version is different. It is 3.21041.29

[aaroh_bits · Accepted solution]

We raised Microsoft ticket and issue is resolved. 

1. Navigate to Power Apps Admin Center
2. Selected the Environment you are working. 
3. Click on Settings on top bar.  
4. Go to User + Permissions >> Security Roles  
5. Under the Security Roles, find the Basic User role , click on  ellipses (...) >> Edit
6. Under Customization tab >>  Select Process >> assign Read access to the Organization
   
   

1. Workflow with OneDrive connection  works without any issue. 
   
   Hope it helps someone. 

[SCTdan]

Confirmed as well, resolved my issue immediately after changing that.

Gotta get the right support rep I guess, my ticket had pretty much stalled.

[abhishekgawde]

This did not work for me. Unfortunately the 2021 Release Wave I, which i thought had resolved the issue for me has not resolved it.

I assigned the Basic User role to the end user, but still the flow does not get triggered and I get the Connection not defined for this service error.

Anything that i might be missing here?

@SCTdan @aaroh_bits 

[SCTdan]

Try to re-share the app maybe?

[sammybridge]

Hi guys,

Just an update on this, I have added the following two properties, both under Customizaton, to the Basic User Security Role and it seems to have worked:

[indhaa]

HI

I cant see your images, it is too small. Can share it again?

[indhaa]

Hi

Can you let me know by giving Read only to Organization, what kind of access Basic User will get. I couldn't find relevant doc on this. Can share the info?

[sammybridge]

Hi @indhaa ,

Here are the 2 changes I made to allow this to work. If you allow Read Only for Organisation, it means the user can read anything within that table which is owned by anyone else in the Organisation.

Thanks

[indhaa]

Hi,

So I tested by changing the 'Process' Read access from 'User' to 'Organization' and it works. But I don't like this means it gives read access to everyone. Does this mean even if it is not shared, user will have access?

I check how it is in my test environment, which doesn't have any issues. The 'Process' is set to User. I think my issues came during export from test to production environment. The connection fails during export.

[sammybridge]

Hi @indhaa 

I don't know if there is another way to fix this unfortunately. I stopped trying after this worked for me. I am the same though and it works in my test environment but not my Production environment. If you find another way, can you please advise me on here?

Thanks

[indhaa]

I will let you know if I find another solution.

Just want to let you know if a user login to the app. it applies the rights permanently.

If we remove the above access, the app works fine for these users. No need to keep it set as above permanently. 

But this is not solution for new users which we need to apply the rights again.  

[marial16]

Hallo,

i am actually facing the same issue trying to export a Solution to a different tenant. The connection between powerapps and a flow that is being triggered through a button in the app is lost. I have tried the steps you propose but still not working.

I also use environment variables and i m getting error messages. Looks like something is not working properly