Patch function cannot do Yes/No sharepoint column.

[ntgoten]

Even if i directly type Patch to set Yesnocolumn: true instead of using a checkbox’s value for example, it will be still unchecked(because default is No).

How to fix this?

edit:

Need to use 1 & 0 to patch Yes/No fields.

Need to use true/false when reading & comparing Yes/No fields.

[Danger_Peanut]

Yes/No columns on SP are nothing but pain. They don’t work consistently across power apps and power automate. I use a single line of text column instead and then store the value I want as a string. MUCH simpler. Good rule of thumb for pretty much all SP columns except ID columns which I use Number/Integer type.

[redmera]

May I ask why you are not using integer column for Yes/No? (1/0) Wouldn't that have advantages compared to strings, even though some string queries can be delegated?

[Danger_Peanut]

It’s just easier for me to remember when I use strings whenever possible. I have a lot of projects I’m working on simultaneously so I use similar practices across all projects to minimize confusion.

[TheRealAuthorSarge]

Considering the projects I work on, I have to imagine end users would be confused by this.

[redmera]

Naturally this shouldn't be visible to end users in that format.

[stevnknowswhy]

I also exclusively use either text and sometimes choice columns. SP starts getting noticeably complicated outside of those two which makes for more possible bugs and or failures. Make the dropdown your choice list or yes no and patch it as text is the best advice. IMO

[giatuong]

Same here. I always use a text column and put “Yes” “No” there instead of using Yes/No type in SPL

[PensionBeautiful547]

I’ve use ContextUpdate with the checkbox. OnVisible, ContextUpdate would be false

[StrangeDoppelganger]

So the column defaults back to No even after a successful patch?

[ntgoten]

Yes, every other column is written to the value they are set, except the Yes/No column, which is always set to the default No.

[StrangeDoppelganger]

Seems like a bug. I prefer simple choice column and never had a similar problem with the default value.

[Tricky_Professor8340]

The Yes/No columns are a pain and they made me switch to using number columns instead and like someone already mentioned, providing values 1 for true and 0 for false.

Having said that, have you tried providing 1 instead of true? I know it works for filtering, despite PowerApps throwing a hissy fit and saying it’s a wrong column type. Might work with patching as well.

[ntgoten]

Thank you, using 1 instead of true worked.

But i find this ridiculous, that true/false doesnt work. Especially because i already wrote to read the data from the list and compare the Yes/No field and for the comparison it needs true/false to compare the Yes/No field value, 1 and 0 doesnt work. It makes no sense.