Replies: 2 comments
-
This same dab.config, when deployed locally, is able to identify the stored procedure and successfully enable the API. Why would the deployment of the webapp error out though? Why can't it identify the stored procedure? Could this have anything to do with database roles on the user-defined-managed identity? |
Beta Was this translation helpful? Give feedback.
0 replies
-
I've managed to resolve this. DAB has now successfully created an API for my stored procedure. Two things are important:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've defined a very standard stored procedure in an Azure SQL database that returns back [3] values [
nvarchar
,bigint
,nvarchar
].Running
SELECT * FROM sys.dm_exec_describe_first_result_set('sp_name', null, 0)
--> returns back valid results.https://learn.microsoft.com/en-us/azure/data-api-builder/database-objects#limitations
I've defined this stored procedure inside the dab.config.
Meanwhile, I get this error when viewing from the WebApp deployment center logs.
If I reference just database tables in my dab.config, that same deployment process succeeds just fine.
For some reason there is some issue with the stored procedure.
Beta Was this translation helpful? Give feedback.
All reactions