Unanswered

Permission settings: Calling SQL Stored Procedure from Power Apps

(1) Share

Report

Posted on by Brenda Edders

I have tested out the new feature and LOVE IT!! However, the permissions are a bit of an issue. I have the stored procedures set up with a service account for execute permissions on SQL Server. I apply the same permissions to the Connection to the database in power apps. My end users with basic user rights cannot execute.

I am a DBO, and developer and I am able to execute just fine.

What are we missing?

Categories:

Power Query

UserError-UsingSQ...

I have the same question (0)

All responses (3)

Answers (0)

JR-06091321-0 4 on at

Like (1)

Report

Hallo,

I get a simular message when i try to run my stored procedure.

The strange thing is that I get no error message at all, when I start the stored procedure when PowerApps is in EDIT mode.
Then everything is working perfect.
When i switch over to RUN mode only, I get this error message.

Can you please inform me, if you found a solution?

Was this reply helpful? Yes No
KA-09091950-0 5 on at

Like (1)

Report

I think I also have the same issue, when running the Power App in developer mode the Stored Procedure works as expected. When I publish and RUN the app, I get an error

{ "error": { "code": 403, "message": "XXx.xxxx is not allowed", "source": "msmanaged-na.azure-apim.net", "path": "choose[3]\\when[1]\\choose\\when[2]",

This seems to be some sort of credentials bug when the connection is published. Has anyone figured out the fix?

Was this reply helpful? Yes No
KA-09091950-0 5 on at

Like (0)

Report

For anyone wondering why the Stored Procedure doesn't work after publishing. You have to leave the SQL connection named exactly as it was imported. I was renaming my connections to keep everything nice and tidy. Unfortunately that was breaking the stored procedure call once it was published.

Was this reply helpful? Yes No