Anyone run into issues with the 'not' operator on the domo API for PDP filters? The docs show that including false for 'not' on a filter will add a PDP rule that the column quals the value. In this example that Attending = 'TRUE' :
{
"id" : 8,
"type" : "user",
"name" : "Only Show Attendees",
"filters" : [ {
"column" : "Attending",
"values" : [ "TRUE" ],
"operator" : "EQUALS",
"not" : false
} ],
"users" : [ 27 ],
"groups" : [ ]
}
However, including 'not' : true, should reverse the value, such that 'Attending' != 'TRUE'
{
"name" : "Not Attending",
"filters" : [ {
"column" : "Attending",
"values" : [ "TRUE" ],
"operator" : "EQUALS",
"not" : true
} ]
}
When I try this, it doesn't seem to matter whether I put true or false for 'not' the result is always that the column = value. Here's an example response. However, the test account I used could only see '123 S Street' whether or not the 'not' operator was true or false.
{
"id": 10143,
"type": "user",
"name": "Def Jam",
"filters": [
{
"column": "address1",
"values": [
"123 S Street"
],
"operator": "EQUALS",
"not": true
}
],
"users": [
1257996134
],
"virtualUsers": [],
"groups": []
}
