Skip to content

DS Archive Support Website

Sections
Personal tools
You are here: Home » Product Manuals DS 3.x » DataSplice 3.0 Administration Client Manual » Queries and Relationships

Queries and Relationships

Within the View Configuration area, pre-defined data queries can be set up. Select Queries and Relationships from the Configuration Section drop-down list to see the appropriate configuration sections.

This area allows an administrator to set up one or more sets of queries that control what data the users see. Also, different types of criteria can be established in conjunction with view and user attributes to allow data selection to vary based on the current client connection. Views can have any number of queries. A parent view can define multiple queries that target the same view to perform different tasks.

Queries and Relationships

Queries are used for many different tasks:

  • Displaying default sets of data to the user, such as the current work list.
  • Finding related records in other views.
  • Creating new records in a target view that are related to the current record.
  • Defining the data displayed in drop lists for fields.

Creating Queries

To create a query:

  1. Select Action > Create New Query from the menu.
  2. In the resulting dialog box, enter the name of the new query.

    Create New Query Dialog

  3. Click OK. The new query now shows up in the list.

Configuring Queries

Selecting a query of interest from the list populates the remaining sections on this screen with the appropriate data.

Basic Settings

Once a query has been selected, the general configuration settings can be configured in the Basic Settings section.

Query Basic Settings

Field Name Description
Target View Specifies the name of the view being targeted by this query. This can be either the view you are currently looking at, or a different view. Selecting a different view creates a navigational relationship between the two views, allowing the user to navigate from the source view to the target view.
Navigation Action This field specifies what action should be taken when the user selects the query from the navigation menu. The available choices are:
  • Create Record -- Creates a new record in the target view using the defaults specified by the query.
  • Display Filter -- Displays the specified filter to allow the user to complete the query criteria before searching for data.
  • Display Grid -- Runs the query and displays the results in grid mode.
  • Display Record -- Runs the query and displays the results in single-record mode.

Navigation Condition This field specifies the condition that must be satisfied for the query to be active. If the condition is not met, the query will not be displayed in the navigation bar. If no condition is specified the query will always be available in the navigation bar.
Offline Condition This field specifies the condition that must be satisfied for the query data to be copied offline. Any number of offline criteria can be defined for a particular view to synchronize different sets of data.
Max Offline Records Specifies the limit to the number of offline records that can be downloaded. 0 is treated as unlimited.

Filters

Filters allow for specific fields of a view to be searched on using a given criteria. The criteria can be a literal value, an attribute, or even an expression. Search criteria can be set up for the selected query in this section. When selected as the default, these criteria control the initial filter settings displayed when a view is first viewed by a user on the Remote Client.

Basic Filter

For additional information about filters, see the following filters section of this manual.

Sorting

If desired, fields can be chosen as a basis to sort the record data. In the Sorting section, select the appropriate field from the Field Name drop-down list. In the corresponding Direction drop-down, choose whether to sort in Ascending or Descending order.

Query Sorting

Note: Sorting should not be defined for queries that are only used to populate data sets, such as those that are identified with a name such as Offline Query, etc. For such queries, the navigation condition is false, so the users will never actually be invoking that query. Thus, it does not make sense to apply sorting to that query. Sorting should only be defined for those queries that the user can explicitly execute, which implies that it has a navigation condition that is set to true or is set to run as the default query.

 


Last modified 2007-02-26 03:35 PM
 

Powered by Plone

This site conforms to the following standards: