[Improvement]: Mappings are ignored when using stored procedures

[JetterMcTedder]

What happened?

When REST enabling a stored procedure and using a mapping, it is ignored and an error is returned where it cannot find the column name. For example I have a stored procedure with 2 inputs name and job. If i put into the mapping that name is full_name, and pass full_name to the stored procedure, it cannot find that column where in a table, it would map full_name to name.

Version

0.8.52

What database are you using?

Azure SQL

What hosting model are you using?

Local (including CLI), Static Web Apps (SWA)

Which API approach are you accessing DAB through?

REST

Relevant log output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[Aniruddh25]

hi @JetterMcTedder, thank you for reporting this issue! This was by design - mappings feature is currently only supported for views/tables. Stored Procedures do have some usage limitations as mentioned in this section:
https://learn.microsoft.com/en-us/azure/data-api-builder/views-and-stored-procedures#stored-procedures

That said, we can definitely enhance this as an improvement.