Hi All,
Background Info
What Works:
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
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
Solved! Go to Solution.
Thank you for this post!!!
Hello together
We have followed all the points, but it still does not work for us:
- All users are users with security role Basic User
- Security role adjusted for process on Read Organization
- Run Only Users for the flows are set. All users are allowed to run the flows
- Solutions are imported with the same account that is used for development. This means that the owner of all artifacts (app, flow, connection references, connection) is the same in all environments.
Our deployment policy is that we can only install managed.
Currently our solution after installing or updating a solution is to open the app in the managed environment in edit mode, remove all flows and re-add them.
Any other ideas on what else can be done to fix the problem?
My experience is you may not edit the apps in the Edit Mode. It breaks your solution. After doing that the App updates dit not came through (although the version number was updated).
My advice is
Thank you for your reply.
Maybe I was not precise enough. Development of all artifacts and deployment is already done with a service account.
The app uses 8 flows. In the dev environment everything works fine (of course). After the managed installation or update in the test environment (where we remove all unmananged layers beforehand) no more flows can be called from the app. It is like the link between the app and the flows is broken (as described in the original problem message at the beginning of this thread). It is not that the connections of the flows are no longer authorized. And we already have a custom solution for the custom connectors, which we import first, then make sure they are reauthorized before importing the solution with the app and flows. OnPrem Data Gateway is not in the game.
And in the test environment?
If it does not work there either I suggest deleting the whole solution(s) and reimport it again.
That might just work. But since this is a customer installation where > 30 people are testing, this would not be such a good idea because it changes the link to the app.
And most importantly, it wouldn't work in the Productive environment because then > 300 users would have to get a new link every time after each update.
For the test environment, my opinion is that is where it is mentioned for, the Prod environment that is indeed critical.
Log a service request with microsoft itself?
Yes I have the same issue too.
When i deploy from Dev to Test, Dev is unmanaged and Test is Managed solution.
One of the flow status is Not Connected after deployed to Test environment.
I need to click connected manually after I deployed to Test. It created an unmanaged layer which is very annoying.
This can cause potential issues if you were to want to get your app pen tested as users are able to query the process table via the api and return the definition of all flows even ones they shouldn't see.
We have been able to resolve this by using the "Power App (V2)" trigger. This then allows you to set run-only permissions for the flow. Here are the exact steps we use.
Hope this is helpful as I have been unable to find an example explaining this.
Update
A small change you don't need to have 2 separate flows as long as on the one with the connections you do step 3.
Hi there, we've encountered a similar issue with one of our customers ("Connection not configured for this service"). They are hesitant to either add users to a security group or alter security roles for other users. Is there any other workaround we can try/recommend to them?
Hi I have the same issue.
I have even deleted slq connections in my development environment, My app and flows just make http requests to an api.
It does not use sql connections directly.
I tried with the solution provided and I got the same error.
@leeal Do you only get this problem once you package up the solution and deploy to a new environment? Or are you getting it in the environment where you developed the app?
@marcosrobles are you able to post a screenshot of the flows section in details for the app and the details screen of the flow?