Share
Report
29Hello,
We are currently building a custom connector to package our public API. We already have an existing OpenAPI 3.0 file which we use as the base for this connector. We know that powerautomate will convert this to Swagger 2.0 internally.
Both OpenAPI 3.0 & Swagger 2.0 define a spec for common parameters for paths, which are re-used for all methods of that path:
2.0: https://swagger.io/docs/specification/2-0/describing-parameters/
3.0: https://swagger.io/docs/specification/describing-parameters/
It seems that when importing/updating our custom connector these common variables are not recognized by power automates UI. Yet the swagger UI & validation perfectly recognize them when enabling the swagger editor in the browser.
After doing some research I found this post from a user with the same problem : https://powerusers.microsoft.com/t5/Building-Power-Apps/Custom-connecter-Issue-while-creating-a-definition-with-Open-API/td-p/901688
Power automate staff claimed it was a gap in the platform
I would like to ask if this is still the case after 2 years?
Thanks in advance!
All responses (
Answers (
