Unanswered

text/plain in custom connector

(0) Share

Report

Posted on by JosL

I've added a custom connector and validated its schema in my PowerApps environment. In the connection tester it works fine, and in the header it clearly states "content-type": "text/plain".

The body returned is text/plain, again, this works in the tester, but when I add this to a button or variable assignment in my PowerApp it says (in the PowerApp) "failed: the data returned in the response is invalid".

If I check with Fiddler, I see the request coming back (/invoke) to the PowerApp in text/plain.

Relevant swagger section for the 200 return code:
responses:
'200':
description: OK
schema: {type: string}

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (0)

v-siky-msft on at

Like (0)

Report

Hi @JosL ,

Can you share more codes or screenshots with your scenario?
It would be better to help you.
Best regards,
Sik

Was this reply helpful? Yes No
JosL 15 on at

Like (0)

Report

Maybe I should restate my question: Does PowerApps support text/plain as a result from a connector instead of JSON?

I ended up writing my own Azure Function and creating a custom connector that does return JSON instead of using the built in connector that is broken. (Azure Automation)

Was this reply helpful? Yes No
victorsijtsma 9 on at

Like (0)

Report

Can PowerApps receive a different type as response from a custom connector?
Only supported types seem to be: Object(json) and binary.

Flow/Power Automate is also allowed string for example

Was this reply helpful? Yes No