You’re offline. This is a read only version of the page.
Hello, i created a simple powerapp that is submitting data to sharepoint List. It is important for me, that the end users are not able to edit the list that the data is submitted to. I've found a workaround and i am submitting the data to a sharepoint list via Power Automate flow with my credentials(i have rights to edit sharepoint list). Everything is working fine if i share the app to the users, but If i add a co-owner and he tries to add something via app i get a following error: <name of my flow>.Run: connection not configured for this service. I do not see failed run in Run history. Taht what the OnSelect property looks like for submit button:
Hello, do you maybe have some information why it is not working. Replying to this advice :"To avoid individual user permissions issues, consider using a service account to run the flow. This account should have the necessary permissions on the SharePoint list. This way, regardless of who triggers the flow from the app, it will always use the service account's credentials.". Account triggering the flow has all permissions. The account is specified in the Manage run-only permissions tab of the flow. For me the odd behavior is, that User can use the app and when the permission is changed to a co-owner it is not possible anymore
Hello, my main question is why if i change his role to user, he is able to use the app. If the role is changed back to co-owner he is unable. I have not added anyone to a flow manually (permission to use it), so for me it is a weird behavior that the user can run it, but the co-owner can not
hey @Bartosz_Pers
this might be because the other user has no permission for the flow i guess. Did u also add the other user as co-owner at power automate flow settings?
Here are some steps that might resolve the issue:
The error message suggests that there's a problem with the connection used by the flow. Since the flow is using your credentials, your co-owner might not have access to the same connection. You need to ensure that the flow's connection is accessible to all co-owners.
Share the flow with your co-owner. Go to your Power Automate flow, and under the "Details" tab, there should be an option to share the flow. Add your co-owner here, giving them the necessary permissions. This will allow them to use the flow with their credentials.
If the above step doesn’t work, your co-owner may need to reconfigure the flow's connection with their own credentials. This can be done by editing the flow and updating the connection details in the actions where the SharePoint list is accessed.
To avoid individual user permissions issues, consider using a service account to run the flow. This account should have the necessary permissions on the SharePoint list. This way, regardless of who triggers the flow from the app, it will always use the service account's credentials.
Ensure that both the app and the flow have the correct permissions set up. The co-owner should have Contributor or Owner permissions on the app, and similar permissions should be granted for the flow.
The OnSelect property for the submit button in your PowerApp is crucial. Ensure it's correctly configured to call the flow. It typically looks like '<name_of_your_flow>'.Run(<parameters_if_any>).
Test the app with different user scenarios – as an owner, co-owner, and a regular user. This will help you identify if the issue is specific to the co-owner role or a general issue with the flow connection.
Let me know if my answer helped solving your issue.
If it did please accept as solution and give it a thumbs up so we can help others in the community.
Greetings
#1
WarrenBelz
388
Most Valuable Professional
#2
MS.Ragavendar
193
#3
stampcoin
147
Share
Report
All responses (
Answers (
