Unanswered

Adding custom connector to Canvas PowerApp: Service could not be created. Error retrieving Wadlmetadata

(0) Share

Report

Posted on by Community Power Pla... Microsoft Employee

Dear,

I've created a custom connector that I want to add to my PowerApp. I've tested the connector in the Custom Connector UI and everything seems to work. However, when I try to add the connector to the PowerApp, I get the following error message:

Service could not be created. Error retrieving Wadlmetadata

I cannot seem to find the problem. Has anyone had this before?

Thanks in advance for the help.

Categories:

Building Power Apps

I have the same question (0)

All responses (5)

Answers (0)

Sort by

jrobertson_ptm 4 on at

Like (0)

Report
Copy link

Link copied!

I'm having the same issue.
Is your PowerApp a regular PowerApp or a PowerApp for Teams?
Was your custom connector created the regular way or via Azure API Management?

Was this reply helpful? Yes No
jrobertson_ptm 4 on at

Like (1)

Report
Copy link

Link copied!

I was just able to fix it. One of my definitions for a response had some required fields. I removed the required property from the swagger definition and then I was able to add the custom connector.

I believe the issue was that PowerApps doesn't know how to handle a required field in a response definition. I can't guarantee this was the issue but it worked for me.

Was this reply helpful? Yes No
zYx 78 on at

Like (1)

Report
Copy link

Link copied!

It looks like I had some leftover code in the Swagger editor from when I was creating Actions and then deleting them. They remained in the swagger code. Removing them fixed the issue.

Was this reply helpful? Yes No
ValKuppuswamy 4 on at

Like (0)

Report
Copy link

Link copied!

I'm getting the error "Service could not be created. Error retrieving Wadlmetadata" while trying to add a custom connector to a PowerApp. The suggestions provided in this thread didn't seem to work.

Was this reply helpful? Yes No
ValKuppuswamy 4 on at

Like (0)

Report
Copy link

Link copied!
I was able to narrow it down to having an array query parameter (see an example below) for an endpoint in the swagger file. Has anyone run into this before? Any workaround to handle this?
{ "name": "<parameter_name>", "in": "query", "description": "Description.", "type": "array", "items": { "type": "string" }, "collectionFormat": "csv", "x-ms-summary": "<parameter_name>" },

Was this reply helpful? Yes No