I have a Power App that is part of a solution that is using tables and stored procedures from an on-prem SQL Server database. I have a full ALM solution with DEV, TEST and PROD environments. At some point a few weeks back when I added a new stored procedure, a bunch of my other connections somehow "broke" and I get a 403 error that only shows up after I publish. The only way to fix it is to delete all of my stored proc connections (in the data section within the app) and re-add all of them. I have 20+ stored procs so this has become quite a pain. I learned the hard way not to change a stored proc either since that seems to break Power Apps, so I always create a new version and then add a new one. I also remove the old ones once I no longer am using them.
Everything works fine in DEV until I publish and/or export the solution and move it to TEST. Is there something I might have done to cause this issue? Or is this a known bug? I have an on prem database and am using an on-prem gateway. I also have connection references set up for my solution so moving form DEV -> TEST -> PROD works well. Also, another developer recently added Dataverse tables in the same solution but used in a different app. I don't think this would cause this problem, but maybe someone else knows if that would cause a conflict?
Any suggestions would be much appreciated.
Example error: SP_MyStoredProc.dbospExampleStoredProc failed: { "error": { "code": 403, "message": "Procedure dbo.spExampleStoredProc is not allowed", "source": "XXXe03594-27cb-ef40-9542-2b6ea670e00f.09.common.usa002.azure-apihub.net", "path": "choose[2]\\when[1]\\choose\\when[2]", "policyId": "", "clientRequestId": "XXXa0fcb-0aea-406d-9cb5-15ef08db8e84", "dreeSet": "true" } }
