Predicates - Nextedy Documentation

Predicate Types

Type	Description	Operators
Binary predicate	Compares a single property value against a constant	`eq`, `ne`, `gt`, `ge`, `lt`, `le`, `contains`
Composite predicate	Combines multiple predicates with logical AND or OR	`and`, `or`
Collection quantifier	Evaluates a predicate across multi-valued navigation properties	`any`, `all`

Binary Predicates

A binary predicate compares one entity property against a value using a comparison operator.

Syntax

Full form:

propertyName:
  operator: "value"

Shorthand equality form (equivalent to eq):

propertyName: "value"

Comparison Operators

Operator	Alias	Supported Types	Description
`eq`	`==`	String, number, boolean	Exact equality. Case-sensitive for strings.
`ne`	`!=`	String, number, boolean	Inequality.
`gt`	`>`	Number (Integer, Double, Long), date	Greater than.
`ge`	`>=`	Number, date	Greater than or equal.
`lt`	`<`	Number, date	Less than.
`le`	`<=`	Number, date	Less than or equal.
`contains`	—	String	Case-sensitive substring match.

The gt, ge, lt, and le operators work with Integer, Double, and Long values. They are not applicable to string or boolean properties.

Examples

Equality — exact match on a property value:

title:
  eq: "System Requirement 1"

Shorthand form produces the same result:

title: "System Requirement 1"

Both translate to the Lucene query title:"System Requirement 1". Inequality — exclude a specific value:

status:
  ne: "rejected"

Numeric comparison — range filtering on numeric properties:

priority:
  gt: 3

Inclusive upper bound:

severity:
  le: 5

String contains — substring search (case-sensitive):

title:
  contains: "safety"

Null Predicates

Null checks test whether a property has a value or is empty. Use eq or ne with a null value.

Null predicates (eq: null and ne: null) are currently non-functional in this release. The syntax below describes the intended behavior, but predicates that compare against a null value will not produce correct query results until this is resolved. Avoid relying on null predicates in production sheet configurations. Track this limitation through your support channel for status updates.

Property has no value (intended behavior):

title:
  eq: null

Property has a value (intended behavior):

title:
  ne: null

Expression	Lucene Translation (intended)	Meaning
`prop: { eq: null }`	`NOT HAS_VALUE:prop`	Property is empty
`prop: { ne: null }`	`HAS_VALUE:prop`	Property has a value

The HAS_VALUE pseudo-field is a Polarion-specific Lucene construct for checking property existence. When the null predicate feature is operational, the server API translates null predicates into this syntax automatically.

Composite Predicates

Composite predicates combine multiple sub-predicates using logical AND or OR operators.

AND Predicate

All sub-predicates must match. Wrap conditions in an and array:

and:
  - status:
      eq: "approved"
  - priority:
      gt: 2

Translates to Lucene: (status:"approved") AND (priority:{2 TO *})

OR Predicate

Any sub-predicate may match. Wrap conditions in an or array:

or:
  - status: "draft"
  - status: "in_review"

Translates to Lucene: (status:"draft") OR (status:"in_review")

Nested Composites

AND and OR predicates can be nested to build complex filtering logic:

and:
  - priority:
      ge: 3
  - or:
      - status: "approved"
      - status: "in_review"

Resulting Lucene: (priority:[3 TO *]) AND ((status:"approved") OR (status:"in_review"))

AND binds more tightly than OR. Each operand in composite predicates is parenthesized during Lucene translation to maintain correct evaluation order. Use explicit nesting when combining AND and OR to ensure predictable results.

Collection Quantifiers

Collection quantifiers evaluate predicates against multi-valued navigation properties (related entity collections).

Quantifier	Alias	Description
`any`	`some`	Returns `true` if any element in the collection matches the condition
`all`	`every`	Returns `true` if all elements in the collection match the condition

any uses short-circuit evaluation — it stops at the first match for performance. all returns false at the first non-match. It is used in validation rules and completeness checks.

Collection quantifiers are used for filtering across related entity collections. The exact query syntax for any and all with nested property conditions depends on the entity type metadata and the relationship configuration in the data model.

ObjectId Predicates

Query a specific entity by its Polarion work item ID:

objectId: "UN-001"

With project prefix:

objectId: "myProject/UN-001"

The project prefix format project/id expands to a compound query: project.id:"myProject" AND id:"UN-001".

Data Property Predicates

Predicates on entity data properties are validated against the entity type schema before execution. Only scalar (non-navigation) properties are supported in direct predicates. The server API processes the where clause by:

Extracting all property names from the predicate
Matching each property against the entity type metadata
Rejecting predicates that reference unknown or navigation properties
Combining validated predicates with AND logic

If a predicate references a property that does not exist in the entity type metadata, the query will fail with a validation error. Always use property names exactly as defined in the data model.

For navigation property filtering (document or project scoping), use the dedicated constraint system. See Document Filtering and Query Context.

Document and Project Predicates

Document and project predicates filter by navigation properties and are extracted separately from data property predicates. Document filtering:

document:
  moduleName: "Requirements"
  moduleFolder: "Specifications"

Project filtering:

project:
  id: "myProject"

Cross-project queries are not supported. All queries execute within a single project scope. The project predicate is used to specify which project to query, not to query across multiple projects simultaneously.

When the project predicate contains only an id field, the server API uses a simplified Lucene query (project.id:value). More complex project predicates undergo full predicate evaluation against the Project entity type metadata.

Where Clause Merging

When multiple filter conditions are combined (for example, from user-applied filters and sheet configuration constraints), Powersheet merges them using these rules:

Scenario	Merge Behavior
Two AND predicates	Arrays are concatenated
Two OR predicates	Arrays are concatenated
AND + OR	The OR predicate is wrapped inside the AND
Property conflicts	The second value overrides the first
Empty/undefined	Ignored silently

Lucene Translation Summary

Predicates are translated to Polarion Lucene query syntax before execution against the data store.

Predicate	Lucene Output
`name: "John"`	`name:"John"`
`count: 5`	`count:5`
`prop: { ne: "X" }`	`NOT prop:"X"`
`prop: { gt: 3 }`	`prop:{3 TO *}`
`prop: { ge: 3 }`	`prop:[3 TO *]`
`prop: { lt: 10 }`	`prop:{* TO 10}`
`prop: { le: 10 }`	`prop:[* TO 10]`
`prop: { eq: null }`	`NOT HAS_VALUE:prop` (intended; see known limitation)
`prop: { ne: null }`	`HAS_VALUE:prop` (intended; see known limitation)
`and: [...]`	`(...) AND (...)`
`or: [...]`	`(...) OR (...)`

Complete YAML Example

A source configuration with predicates applied through the where clause:

sources:
  - id: filtered-requirements
    title: Active Requirements
    model: rtm
    query:
      from: UserNeed
      where:
        and:
          - title:
              contains: "Safety"
          - or:
              - status: approved
              - status: in_review
          - priority:
              ge: 3
      expand:
        - name: systemRequirements
    constraints:
      applyCurrentDocumentTo: UserNeed

This query:

Targets UserNeed entities
Requires title to contain the substring Safety
Limits results to approved or in_review status
Requires priority of 3 or higher
Expands the systemRequirements navigation property
Scopes results to the current document

Predicate Type Compatibility

The following table summarizes which Polarion custom field types are compatible with each operator:

Field Type	`eq` / `ne`	`gt` / `ge` / `lt` / `le`	`contains`	Null checks
`string`	✅	—	✅	✅
`integer`	✅	✅	—	✅
`float`	✅	✅	—	✅
`boolean`	✅	—	—	✅
`date`	✅	✅	—	✅
`richtext`	✅	—	✅	✅
`currency`	✅	✅	—	✅
`duration`	✅	✅	—	✅

EntityQuery — top-level query structure with from, where, expand, and orderBy
Expand Clause — loading related entities inline
Query Context — runtime parameters for query execution
Document Filtering — scoping queries to specific documents
Binding Syntax — property path syntax used in predicate property names
Sources — configuring data sources that use predicates

​Predicate Types

​Binary Predicates

​Syntax

​Comparison Operators

​Examples

​Null Predicates

​Composite Predicates

​AND Predicate

​OR Predicate

​Nested Composites

​Collection Quantifiers

​ObjectId Predicates

​Data Property Predicates

​Document and Project Predicates

​Where Clause Merging

​Lucene Translation Summary

​Complete YAML Example

​Predicate Type Compatibility

​Related Pages

Predicate Types

Binary Predicates

Syntax

Comparison Operators

Examples

Null Predicates

Composite Predicates

AND Predicate

OR Predicate

Nested Composites

Collection Quantifiers

ObjectId Predicates

Data Property Predicates

Document and Project Predicates

Where Clause Merging

Lucene Translation Summary

Complete YAML Example

Predicate Type Compatibility

Related Pages