custom connector consistantly using wrong Content-Type Header

[AlaskanPowrUser]

I was successfully able to create a custom connector by importing a Postman Collection where the API calls are working correctly in Postman. The headers contain Content-Type application/x-www-form-urlencoded

Now, when I use the custom connector in powerapps, it requests the Content-Type value as a parameter for the custom connector function. I supply the application/x-www-form-urlencoded value. as seen below: 

Notice, the custom connector even has it's default value set correctly. 
But you can also see my error. It's super vague "there was an error" 
Under further investigation, i look at the network call for the request, and i see this: 

I don't understand why powerapps is still making this call with the wrong content-type header?????  I have it supplied in SO MANY places including default values, it should not be using application/json

[Syndicate_Admin]

Sorry, the first screenshot is too small to see the content. How are you providing the content-type header?

Here is how to do it: https://powerusers.microsoft.com/t5/Connecting-To-Data/Custom-Connector-Header-quot-content-type-quo...

If this reply answers your question or solves your issue, please ACCEPT AS SOLUTION ☑️. If you find this reply helpful, please consider giving it a LIKE 👍.

[Syndicate_Admin]

Hello

i also have a similar problem when using a custom SOAP connector. I read the full day all the possible solutions but i can't figure out to let the flow trigger the webservice. I recieve the following error message: "The provided input content is not valid: 'The provided content-type header value 'text/xml; charset=UTF-8' is not well formed.'."

Attached u can find some screenshots which shows the policy to overrite the content-type header and the successful test from the custom connector page. Any Clue?

I also recieve the same error message if i only use "text/xml" as Content-Type.

Custom Connector Policy for Content-TypeTest of the Custom ConnectorError Message in Flow

[Syndicate_Admin]

I suspect the semicolon or equal character might be throwing it off. Try the following:

• Set a connection parameter called "charset" and set to UTF-8
• Set the header with this pattern @connectionParameters(‘charset’, ‘’)

Look at this documentation: https://docs.microsoft.com/en-us/connectors/custom-connectors/policy-templates/setheader/setheader

If this reply answers your question or solves your issue, please ACCEPT AS SOLUTION ☑️. If you find this reply helpful, please consider giving it a LIKE 👍.

[Syndicate_Admin]

I found the solution. The header was not well formated in swagger. There was a line break at the end. The connector was exported from postman, maybe a problem on this side. Unfortanaly the Test was okay, the Flow brought up the message so i'm looked at the wrong place to fix this error. Thanks for your reply. My case is solved.