Custom Connector: Optional Fields Become Required in PowerApp

(0) Share

Report

Posted on by C-Jac

I’m having an issue with a Power App I've developed, where I've created a custom connector that connects to an API I built myself. The API has several optional fields that I can successfully use when testing the connector directly, but things change when I connect the Power App to this custom connector.

Once connected, all the optional fields are treated as required, and I get an error stating that there are fields that must be updated but aren't.

Here’s what I’ve tried:

Ensuring that the API defines these fields as optional
Testing the connector independently with the optional fields filled and unfilled

My question: How can I ensure that the optional fields retain their optional status in the Power App? Any guidance or solutions would be greatly appreciated!

Thank you so much for your help! 🙏

Categories:

Connector development

I have the same question (0)

All responses (3)

Answers (0)

Michael E. Gernaey 53,433 Super User 2025 Season 2 on at

Like (0)

Report

Hi

Please share pictures of your App, of your Connector, of your Expressions, of the exact error etc. Hard to tell you how to fix it without that.

Was this reply helpful? Yes No
Suggested answer

MS.Ragavendar 5,011 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

Kindly share the Test Connector details and Power Apps Fx formula.

In-addition to that also show the datasource properties if its sharepoint check the columns are required or not or If its SQL check those columns are not allowing null values.

Was this reply helpful? Yes No
RBoneck 415 on at

Like (0)

Report

Had to do a double take because I thought I might have written this question and forgotten that I'd done so!

I am having the exact same problem, although I did not create the API that my custom connector is for. Otherwise, all of what you said applies. I have several optional fields that are correctly defined as optional for that action in the API and in the custom connector, but when I added the connector to the app and tried to use that action, the app said "missing column" and listed every single field in turn as I added the one it asked for. It ended up saying that every single field defined for this action was necessary to run it, which is certainly incorrect.

Testing that action in the custom connector itself works without issue, and testing that action in a flow also works without issue. This is only a problem in the power app! Please give an update if you find a solution, and I will do the same.

For now as a workaround I think I will be calling a flow from the app instead, since I worry that if the app wants every single field that action is defined with, even if I fill them with blank or the existing info, that means in the future if I add more fields to that actions definition it may cause an error in my app. Good luck with your issue!

Was this reply helpful? Yes No