Unanswered

Creating/Updating a custom connector from a Postman collection

(0) Share

Report

Posted on by Community Power Pla... Microsoft Employee

Hi,

Im trying to negotiate a case where i am provided with an openapi 3.0 YAML file to update a custom connector.

Since custom connectors currently only support openapi 2.0 i have tried importing the file to postman and exporting it to a postman 2.1 collection. During import Power Platform sets all query parameters to required for some reason even though its not specified in the JSON.

To be clear, parameters that are not specified as required seem to default to true.

Has anybody encountered this problem and found a solution to it?

Regards,

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (2)

Answers (0)

joshwelch90987 2 on at

Like (0)

Report
Copy link

Link copied!

I have facing similar kind of issue while updating a custom connector with pets table. But didn't find any solution yet.
Maybe some here found some sort of solution. here.

Was this reply helpful? Yes No
eleung83 232 on at

Like (0)

Report
Copy link

Link copied!

I just tried converting an openapi v3 spec file to a postman 2.1 collection and got the same error. Seems like Postman collections don't support optional/required parameters, and the import automatically treats them as required.

I retried importing the same as a swagger 2/OpenAPI 2 and it default imports the parameters as optional parameters. You can convert the OpenAPI3 format to swagger 2 using npm modules e.g. https://www.npmjs.com/package/api-spec-converter (I used this for converting the ones we use)

This should hopefully no longer be needed come September

Was this reply helpful? Yes No