Quote:
Originally Posted by theducks
Code:
#customfielname:true and not #customfieldname: true
we use the Not construct because the tri-state field. False and undefined are treated as False in the search
remember the # must be included for any custom field name used in searches |
Too BAD the docs dont seem to tell you that!! All of their examples are of non custom field searhces so how are we supposed to know about the "#" sign?