Rules for queries

You can use either the url query field or the fixed filters to build queries in DG3. The syntax of the two are the same. Fixed filter will take presidency of the url query fields, so fixed filters can be used as an security measure in your application.

The search format

Field1=value1&Field2=value2&Field3=value3

This is the basic format. Field is a table field and the value can be any valid field value including ? and *. You can add a < or > as the first value to sort descending or ascending. If equal to is not what you want to query on, you can add a space and the operator you want to use instead.  Two field with the same name will be used as field=value1 or field=value2.

Field1=value1&Field2=>value2&Field2=value3

This means Field1=value1 and (Field2=value2 or Field2=value2) and sort ascending on field2.

You can also use not, >, >=, <, <= and between. The string blank can be used to test for blank strings as Field1= is ignored.

Field1=> >10&Field2= not blank&Field3= between 50 to 200

This mean find any record with field1 greater then 10 and field2 not having a blank value and field 3 is between the numbers 50 to 200, and return the list ordered by field1.

=current date between FromDate to ToDate and current time < ToTime

To use a = as the first character means that this is raw queries and if used in fixed filters, nothing from the url query string is added unless as livetext.. The example finds all records that is between the field FromData and ToDate and ToTime is less than the time now.

Add sorting to query string

To sort ascending or descending you can add a > or < as the first character after the = in the filter. This works in both url filters and fixed filters, but not in raw filters.

datecreated=>&timecreaded=<

Do sort ascending on datecreated and descending on timecreated.

Distinguish between tables in query string

What you add for a table in a fixed filter is for that table. To distinguished between tables and DQLs using url query strings, you can use the name given the dataview as prefix. If you have a table named Contacts, you simply use the form Contacts.field1=value1.

Contact.field1=value1&field2=value2

This means that you have added a query for field1 in Contacts and field2 for Contacts and any other query.

Special field names for DQL query strings

You can send data-entry fields to DQLs using query strings as well. All DQLs in DG3 have 4 fields that can be used for data-entries inside the DQL. These fields are simply named field1, field2, field3 and field4. They are then used in the DQL in the form data-entry field1-4.

?field1=PREP&Articles.createddate=> >=current date&dqlgetitems.field2=blue&dqlgetarticles.field2=green

The query string with the meaning data-entry field1 with value PREP for all the DQLs and query field createddate sorted ascending and today of later for the table named Articles. Then set data-entry field2 for dql called dlqgetitems to blue and data-entry field2 for dql named dqlgetarticles to green. Then this will take care of three dataview on the page on with a Table as input and two different dqls on the others.

for Articles with prefix = data-entry field1 and color = data-entry field2;
list records
  title.

How to use in the DQL