Because the OData service must translate filter conditions into a format that is understood by the reporting engine, the OData feature is currently unable to handle some complex filter conditions that might be provided in very advance interactions. These conditions are noted below, along with the error messages the user will see when the condition is encountered:
Error message: "Parenthetical expressions are not supported"
Occurs when a user attempts to use a parenthetical expression within the filter section of the request. For example:
EffectiveStart <= Current Date AND (EffectiveEnd >= Current Date OR EffectiveEnd is null)
The parentheses characters ( ) are allowed in string constants, but they're not allowed as part of the expression. For example, FirstName eq 'Joe(' is an allowed comparison.
Error message: "Invalid OData filter format"
Occurs when the filter syntax or format cannot be understood by the OData service
Error message: "Single boolean value is not supported"
Occurs when the filter contains a literal true or false (without the use of an expression)
Error message: "Expression does not result in a true or false value"
Occurs when the filter can’t return true or false (invalid constant was used)
Error message: "Query contains conditions that the reporting engine does not support"
Occurs when expressions contain a language construct that isn’t supported by the Dayforce reporting engine. The reporting engine supports the following constructs where supported operators include those listed under the error message "Query operator '{0}' is not supported by the reporting engine":
- Field operator constant (for example,
Firstname eq 'Joe') - Constant operator field (for example,
'Joe' eq FirstName)
Error message: "Nested expressions are not supported"
Occurs when expressions are defined within other expressions. It's likely that the "Parenthetical expressions are not supported" error will be thrown first.
Error message: "Unsupported filter expression found containing value on both left and right side of operand"
Occurs when a constant is used on both side of the operator (for example, 'Joe' ne 'John')
Error message: "Unsupported filter expression found containing field name on both left and right side of operand"
Occurs when a property is used on both sides of the operator (FirstName eq LastName)
Error message "Query operator '{0}' is not supported by the reporting engine"
Occurs when a filter uses an unsupported operator.
Supported operators include:
- Logical operators:
- Equal (eq)
- Not Equal (ne)
- Greater Than (gt)
- Greater Than or Equal (ge)
- Less Than (lt)
- Less Than or Equal (le)
- And
- Or
Unsupported operators include:
- Logical operators:
- Not
- Arithmetic operators:
- Add
- Sub
- Mul
- Div
- Mod
Error message: "Query is not supported"
General error occurs during the parsing of the OData request. This error basically means that all other error messages didn't apply and OData doesn't know what to do with the request or how to describe the problem. This shouldn't happen given our expected use of OData (via business-level analytical tools such as Microsoft Excel and Power BI).