The parameter value is a constraint the documents need to match to not be filtered from the result set. The syntax is different from those you specify in case you run a Lucene search. As in queries you check the property values of the child documents. If the property name you need to match is a alphanumeric token, you do not need to encode it (e.g. Year=2019 ). If it has a space, used $[...] as delimiters for the property name. For instance $[Customer Reference] . This is similar to the encoding used for Lucene queries with the Display Table Macro. You may also use ${...} or $<...> as delimiters. But there is no reason to do so since property names should not contain special characters. We recommend to use the square brackets ($[...] ) since these are also used for Lucene queries of the property name contains a space (see Search Tips). Values that have no spaces and are plain tokens need not to be encoded to compare with a property property value (e.g. $[Zip Code]=45672. In case there is a space, you can use quotes as in $[Customer Reference]="123 ABC" . You may also compare the property value of the document in the result set with a property value of the document the macro is part of: $[Customer Reference]=${Default Customer Reference} You may combine your property constraints by the following Boolean operators. Operator | Description |
---|
& | AND - both properties need to match | | | OR - only one of the two properties need to match | ! | NOT - only true if the property does not match. |
Use parentheses to group your expressions. Example Box |
---|
title | Example Matcher Expression with !, |, and & |
---|
|
Code Block |
---|
| !($[Property A]="Value 1" | !$[Property B] = "Value 2") & $[Property C] = "Value 3" |
|
Currently the projectdoc Toolbox does not support list searches or comparisons with greater than or less than. Only exact matches are supported. |