salesforce "get all" boolean conditions fail

[cromulus]

Describe the bug
Boolean conditions in the salesforce node fail with the error:
id,name,type FROM Account WHERE Is_this_a_food_pantry__c = '{{true}}' ^ ERROR at Row:1:Column:40 value of filter criterion for field 'Is_this_a_food_pantry__c' must be of type boolean and should not be enclosed in quotes

To Reproduce
Steps to reproduce the behavior:

1. create a salesforce node
2. set to "get all"
3. choose resource "User"
4. add condition: "Active" = true
5. Execute node and see error

Expected behavior
I expect to have the node respond with all active users.

Environment (please complete the following information):

• OS: Docker
• n8n Version: 0.181.2
• Node.js Version: v16.15.0
• Database system: postgres
• Operation mode: own & queue

Additional context
Add any other context about the problem here.

[Joffcom]

Hey @cromulus,

Thanks for the report, I take it the error is from where you tried {{true}} as a value and not just true? I suspect we are sending all values as strings rather than different data types which Salesforce looks to be expecting. I will flag this up so we can investigate further.

[cromulus]

I tried both, and got the same error.

[cromulus]

Bump!

[Joffcom]

Hey @cromulus,

Thanks for the reminder on this one, Just to double check when you input {{true}} is it showing as an expression in the UI or do you see {{true}}?

[cromulus]

It's showing as an expression in the UI. green little rectangle with the word "true" in it.

[kevinlitt]

getting same error here.

[TornMarketing]

Any resolution to this? I raised this back in 2020 and figured we would have purged this issue by now

How do we query without quotes?

checkbox_custom_field__c = 'false' ^ ERROR at Row:1:Column:79 value of filter criterion for field 'checkbox_custom_field__c ' must be of type boolean and should not be enclosed in quotes

https://community.n8n.io/t/salesforce-get-with-limits-ie-lastmodified-or-email/3631
#1292

[Joffcom]

Hey @TornMarketing,

Not yet, in theory using the expression should have resolved it as a temporary solution but I got caught up with some other issues.

I will bump this one back up my list and see if I can get it sorted either today or early next week.

[Joffcom]

Quick update, We are tracking this one internally as NODE-182