Properly filter SharePoint Yes/No column.

[tchin-nin]

There is a well known "bug" when working with SharePoint list Yes/No column :

The Yes/No value can not be compare to boolean type true/false. 

Filter(SPList,YesNoColumn = true) will not return all the items with a Yes value .

The workaround is to use 1 or 0:

Filter(SPList,YesNoColumn = 1)

This will return all items with a true value, but the designer shows an error because we are comparing a boolean to a number. 

It would be great to fixe that, as a Yes/No column is indeed a boolean value, we need to be able to compare that to a boolean value in PowerApps. 

Théo

[beebul]

@LanceDelano  WooHoo good news! 🚂=========

[objectivelyLost]

@LanceDelano 

Is this going to break any apps using the former 1/0 in place of true/false workaround?

[eliotcole]

This still appears to be an issue.

eq 1 isn't working, should we be using TRUE, now?

[max81]

Finally! Last week it was still not working, now it seems to be fixed for our tenant:

'Yes No' is the name of my SharePoint column.

I tested these expressions in my formula:

• 'Yes No' = 0 --> delegable! With warning, that Boolean and Numbers can't be compared
• 'Yes No' <> 0 --> not delegable! With warning, that Boolean and Numbers can't be compared
• 'Yes No' = 1 --> delegable! With warning, that Boolean and Numbers can't be compared
• 'Yes No' <> 1 --> not delegable! With warning, that Boolean and Numbers can't be compared
• 'Yes No' = true --> delegable!
• 'Yes No' <> true --> not delegable and wrong results!
• 'Yes No' = false --> delegable!
• 'Yes No' <> false --> not delegable

[JR-BejeweledOne]

@max81 Try filtering it with a second filter option.

I can filter my list by = true/false but as soon as I add a second filter criteria it doesn't return anything at all even though the second filter option works by itself and in conjunction with other filter criteria

[andrewng30]

I am still getting issue when using Filter(sharepoint table, "Yes/No Column" = true).  Still getting all the false records not the true ones and using "Yes/No Column" = 1 get the comparison warning and not delegable.  I am on version 3.21115 of powerapps studio

[JohnP]

This is probably a 5 minute code fix if someone bothered to look into it. But it would also probably break all the workarounds that you guys have found.

[HISD_JSO]

Has anyone noticed that New "Yes/No" collumms default to blank?