I'm trying to surface the error messages my API provides when it has an issue with new POST request. My connector definition correctly validates the 200/400 responses but I can't make PowerApps surface the response body of the 400 message. If I force the "error response" into a 200 response, I can see the body but thats not a workable solution.
Any ideas on how to get access to the response body of a 400 message?
Thanks in advance - Russ
Could you please share more details about the 400 response definition within the OpenAPI file?
If there is response body defined, the Custom connector should be able to get the response through:
The Response or Result here should be the value defined within the Response, in order to get the result.
You may also take a try with the method below:
which should be possible to hold the whole result into a local connection, when trying to run or call the connector.
I wasn't aware of the other methods you have shared. I will do some testing and see if they are usable. The swagger file is very large so I will attempt to distill it down to just the affected definition and retest if you feel that it should be passed through already. I will come back with my results and the swagger file if it is still not working for me
Thanks - Russell
Unfortunately this is still broken and appears to be an issue in PowerApps. I've created a small basic application which you can use with a custom connector to easily reproduce the issue.