You’re offline. This is a read only version of the page.
I am attempting to create a custom connector using the make.powerapps.com portal.
I have tried exporting the OpenAPI(v2) schema from Azure API Management and importing that into the custom connector wizard. I have gone through and checked all of the validation messages on each screen.
However, when I get to the Test tab, I cannot seem to get any response to come through from my API calls. The schema validation for the response fails with 'Property "" type mismatch, Expected: "object", Actual: "string".'
I have also tried creating a custom connector manually, importing a postman collection and am having zero luck getting it to work. Sometimes I get the response schema validation error I mentioned when I test, other times I get back no response at all.
Has anyone tried creating a custom connector lately using the Power Apps portal and actually gotten it to work? If so, I would *love* to see a sample of something that does work or if someone knows how to fix the aforementioned error, I'm all ears. Otherwise to me, this functionality seems broken.
Hi
where is the API management entry? my webAPI is host in a public computer, it can invoke success from cloud flow>http action, but failed from custom connector, the error is 401( Property "" type mismatch, Expected: "object", Actual: "string".)
Property "" type mismatch, Expected: "object", Actual: "string".'
mpapas - would you please share some more details about "I added "https://flow.microsoft.com" to the CORS policy of my APIM instance, everything started working." -- thanks a lot
No, that wasn't it. I had the API key. I even tried just setting it to anonymous on the APIM side.
But I figured out my problem. Once I added "https://flow.microsoft.com" to the CORS policy of my APIM instance, everything started working.
When you setup your connector are you passing in a subscription key, API key or some other form of authentication (what authentication are you using)? I was receiving that error until I passed in the appropriate key to authenticate who I was. At that point it started working fine. The message was frustrating and a bit vague, but once I found what I was missing that helped.
#1
WarrenBelz
146,660
Most Valuable Professional
#2
RandyHayes
76,287
Super User 2024 Season 1
#3
Pstork1
66,004
Most Valuable Professional
Share
Report
All responses (
Answers (