When defining your simple queries,
through the Simple query editor, the Conditions
folder contains all the conditions the query must satisfy, and
they are classified as follows:
Searching conditions with
empty strings are implemented differently when using Oracle and SQL Server.
See how to use
empty strings in query conditions.
The next picture presents an example of a Simple Query with a filter
condition:
Service Studio provides a Query
condition editor where you define and edit the conditions of your
simple query.
Query
Conditions
The query conditions defined in the Conditions
folder are evaluated at runtime, and the query returns all the rows satisfying
all of its conditions.
|
|
|
Right-click the Conditions folder
in the Simple query editor and
select the Add condition operation.
The Query condition editor
is launched. |
Simple queries do not allow
you to make conditions using null values. For that use an advanced
query.
Query Conditions Evaluation
Order
The conditions of your simple query are evaluated
in the following order:
inner joins
in the order they are displayed in the Conditions folder;
outer joins
in the order they are displayed in the Conditions folder;
filters in the order
they are displayed in the Conditions folder.
You can change the order of conditions within
the inner joins, outer joins and filters. Simply right-click the condition
and select the Move Up or Move Down operation.
Designing Search/Filter Conditions
Designing a query
for searching/filtering records in a list, requires you to handle
values that aren't specified in the criteria fields, like in the following
example:
In this case, use the IsSearchParameter
property of the query parameters:
by default a query parameter has this property set to No,
but once set to Yes, the query ignores
all conditions that are
using this query parameter if its value is not specified.
For the example above, setting the IsSearchParameter
property of the 'NetworkName' query parameter to Yes,
allows you to simplify the query to the following:
See Also
Simple Query
Editor | Types of Joins | Query
Condition Editor | Advanced Logic
Canvas
icon and specify
the relationships between entities. In a simple query you can have inner joins (An inner join between entity A and entity B means that the result of
the query containsonly the records of entity A that have a matching record
in entity B.)
and outer joins (An outer join between entity A and entity B means that the result of
the query containsall the records from entity A whether or not it has
matching records in entity B.).
Learn more about Types of Joins.
icon and specify what must be satisfied
by the records of the query result.