Page Comparison

...

Performs relational database queries on domain SQL database.

XPath
XPath of data model to bind control. If not set uses current node on data model.

Validation Group
Name of validation group rules before executing query. When any rule is failed, error is shown on screen and query is not executed.

...

Design

Auto Search
Specifies the query control should perform a search immediately when visible. Visibility of control can be controlled by Rules or Section Name properties. When Filter content is not visible when this attribute is set to True value Filter content is not visible.

Auto Select All (v4.5)
Specifies the query result picker is must be shown. The result picker allows selecting individual rows to edit. If you work with too many rows, a picker is a better method for performance. When set to True, all matching rows are immediately imported.

Clear First
Specifies the before query results populated on data model all existing records are removed.

Rules

Section Name

Validation Group
Name of validation group rules before executing the query. When any rule is failed, an error is shown on the screen and the query is not executed.

Dynamic Rules

Data

Bound XPath

XPath
XPath of data model to bind control. If not set, uses current node on the data model.

Target XPath
Specifies the xpath of target container node to import query results. Specified xpath is relative to the parent of the current node not XPath attribute.

For example, use "Filter" node for XPath attribute and use "Results" xpath for TargetXPath attribute.

<Data>
	<Filter>
		<SearchField />
	</Filter>
	<Results>
		<Row>
			<Column />
		</Row>
	</Results>
</Data>

Query Syntax

Relational database queries uses use special markup to specify the query to execute. Query structure is similar to SQL Select command, but you may use sub queries subqueries and join clauses automatically handled.

Query Structure

<Query

Start=""
Start index of results to fetch. If not specified 0 value is used.

...

Name="MyColumn"
Name of column or relation path. Please see Column Name for more information. Required.

Formula="None">
Aggregation formula like count, max etc.  If not specified no aggregation is applied. Please see Formula for more information. 

<Properties>
Column specific properties. Currently  

...

Name="MyColumn"
Column name or relation path to criteria to apply. Please see Column Name for more information. Required.

Comparison="Equals"
Comparison method of criteria like equals or greater etc. If not specified Equals value is used. Please see Comparison for more information. 

Condition="And"
Condition of criteria to merge with previous criteria in list. "And", "Or" values are valid. If not used "And" value is used.

Formula="None">
Aggregation formula like count, max etc. If not specified no aggregation is applied. Please see Formula for more information. 

<Value></Value>
Value of criteria. Value can be specified in static value or template format like "{{Code}}" or "000-{{Code}}-1111" to dynamically evaluate.
If not specified value used as empty string.
You can use "NULL" string value to specify null value.

<Properties>
Criteria specific custom properties. Currently IgnoreIfEquals only used.

<

...

/

...

Properties>

...

<IgnoredValues>
The list of values to ignore

...

criteria completely. For example;

...

when product name criteria is set to empty value you may want to list all

...

products, not

...

empty named products.

<Value></Value>
Value of criteria.

</Properties>IgnoredValues>

</Criteria>

<Criteria> ............ </Criteria>

...

Name="MyColumn"
Column name or relation path to apply order. Please see Column Name for more information. Required. 

Type="Ascending"/>
Type of ordering. "Ascending", "Descending" values are valid. If not specified "Ascending" value is used.

...

Name="">
Name of table relation to get rows as child. If relation is not found in table definition error is thrown.

</Query>

</SubQueries>

</Query>

...

Formula specifies the method of evaluation of row values. Formula enumeration can be one of following values;

Comparison

Specifies the comparison method of criteria value.

...

Column Name

Column names can be specified as directly column name or relation path. Relation paths can be specified as "Relation.Relation.Column" format.

 For example, you can use the following values as column names for above relational database model.

Example Query

Following The following query returns the all customer name names and count counts of orders by product name criteria. Each row also contains the list of related customer orders as a child rows.

<Query>
	<Parameters>
    	<TargetSchema>Customer</TargetSchema>
		<TargetTable>MySchema</TargetTable>
	</Parameters>
	<Columns>
		<Column Name="Name" Formula="None" />
		<Column Name="Orders.Id" Formula="Count" />
	</Columns>
	<Where>
		<Criteria>
			<Criteria Name="Orders.Product.Name" Comparison="Like">
				<Value>{{ProductName}}</Value>
				<IgnoredValues>
					<Value></Value>
					<Value>*All*</Value>
				</IgnoredValues>
			</Criteria>
		</Criteria>
	</Where>
    <Order>
		<Order Name="Orders.Product.Name" Type="Ascending"/>  
	</Order>
	<SubQueries>
		<Query Name="Orders">
			<Columns>
				<Column Name="Id" />
				<Column Name="ProductId" />
			</Columns>
		    <Order>
				<Order Name="Product.Name" Type="Ascending"/>  
			</Order>
		</Query>
	</SubQueries>
</Query>

...