GlideQueryCondition - Global
-
- UpdatedJan 30, 2025
- 3 minutes to read
- Yokohama
- API reference
The GlideQueryCondition API provides additional AND
or OR
conditions that can be added to the current condition, allowing you to build complex queries.
In the case of addCondition(), an implied AND
is added.
- addActiveQuery()
- addInactiveQuery()
- addJoinQuery()
- addNotNullQuery()
- addNullQuery()
- addQuery()
If there is a complicated set of AND
and OR
queries, a single encoded query containing all conditions simplifies the query creation. To simplify the query creation, create a query in a list view,
right-click the query, and select Copy query. It creates a single encoded query string to return your result set. Use that string as a parameter in an addEncodedQuery() method call.
Always test queries on a sub-production instance prior to deploying them on a production instance. An incorrectly constructed encoded query, such as including an invalid field name, produces an invalid query. When the invalid query is run, the invalid part of the query condition is dropped, and the results are based on the valid part of the query, which may return all records from the table. Using an insert(), update(), deleteRecord(), or deleteMultiple() method on bad query results can result in data loss.
You can set the glide.invalid_query.returns_no_rows system property to true to have queries with invalid encoded queries return no records. In some cases, the query may still return records in API results even when glide.invalid_query.returns_no_rows is set to true. This happens in queries where an invalid query term is used with a WHERE operator. In such queries, the WHERE operator ignores the invalid term(s) but still interprets and returns the rest of the query statement. For more information about this system property and its functionality, see Available system properties.
GlideQueryCondition - addCondition(String name, String oper, Object value)
Adds an AND condition to the current condition.
Name | Type | Description |
---|---|---|
name | String | The name of a field. |
oper | String | (Optional) The operator for the query. If you do not specify an operator, the condition uses an equals operator. |
value | Object | The value to query on. |
Type | Description |
---|---|
GlideQueryCondition | A reference to a GlideQueryConditon that was added to the GlideRecord. |
Example
Scoped equivalent
To use the addCondition() method in a scoped application, use the corresponding scoped method: addCondition().
GlideQueryCondition - addOrCondition(String name, String oper, Object value)
Appends a 2-or-3 parameter OR condition to an existing GlideQueryCondition.
addOrCondition() works in conjunction with any of the addQuery()methods to OR
the specified query parameters to
the query previously constructed using addQuery().
addOrCondition() is typically called with three parameters; table field,
operator, and comparison value. It can be called with only two parameters, table field and
comparison value, such as qc.addOrCondition('category', 'software');
. The
operator in this case is assumed to be "equal to".
Name | Type | Description |
---|---|---|
name | String | Field name |
oper | String | (Optional) Query operator. The available values are dependent on the data
type of the value parameter. Numbers:
Strings (must be in upper case):
|
value | Object | Value on which to query (not case-sensitive). Note: All passed in arrays must
contain a minimum of two elements. Single element arrays are not
supported. |
Type | Description |
---|---|
GlideQueryCondition | A reference to a GlideQueryConditon that was added to the GlideRecord. |
Example
Example
To group AND/OR statements such as (state < 3 OR state > 5) AND (priority = 1 OR
priority = 5)
use code similar to the following:
Scoped equivalent
To use the addOrCondition() method in a scoped application, use the corresponding scoped method: addOrCondition().