I have prepared custom connector to functions besed on postman solutions. THe functions are exposed as API managements with Ocp-Apim-Subscription-Key. the connector is set also with this header security, but when calling function it returns 200 ok with empty results. it seems it uses internal APIM to call our APIM.
I have checked on our APIM side and the calls are successfull. so something must be wrong on translating the response to Powerapps connector tests.
I have used the example with sentinent text api and did the same. how to track the errors?
Could you please share a bit more about the OpenAPI definition file for your custom connector?
Do you define a proper Resposne part within the OpenAPI definition file (for your custom connector)?
Please check if you have defined a proper Response part within the OpenAPI definition for your custom connector. The standard format of OpenAPI definition file as below:
In addition, please check if your RESTful API has returned a proper result. You could consider take a try to test your RESTful API within Postman, then check if the returned result is empty. If the returned result is empty, I think this issue is related to your RESTful API.
More details about customizing connector within PowerApps, please check the following article:
Thank you for some inputs. The point with valid Response part within OpenAPI definition may be right.
However, I have followed this turorial https://docs.microsoft.com/en-us/connectors/custom-connectors/define-postman-collection , and also the one for postman collection create with response saving: https://docs.microsoft.com/en-us/connectors/custom-connectors/create-postman-collection#save-the-req... and then exported to API v1.
Next step was to import this postman collection in PowerApps custom connector. That spoken, I don't know how to check what OpenAPI definition this collection was automatically converted to... Any idea how to check that?
The postman sollution was returning correct response btw.
Hello @abecerra, if it helps you, we switched from custom connector to database connector (we use sql server).
the benefit is that it comes with automaic generation of CRUD UI which you may then finetune, so a great help for begginers.
some drowebacks is that joins are limited, so only usable for simple operations. if you want to make a join 1-many you need to create connecitons to 2 tables and then utilize a lookup.
Reopen responsibly, monitor intelligently, and protect continuously with solutions for a safer work environment.
Join us for an in-depth look at the new Power Apps features and capabilities at the free Microsoft Business Applications Launch Event.
Featuring samples like Return to the Workplace and Emergency Response Applications
Features releasing from October 2020 through March 2021