This appendix provides a detailed example of how to use grid web services to obtain a definition of stored grid definitions (queries and fields). With this information, you can build grid web service XML requests to add filters, fields, and sort criteria to retrieve any data accessed by the predefined queries.
The following terms are used throughout this appendix:
Grid—defines the base query with table used and joins between them. Required security checks based on user ID are embedded in these queries when needed. Therefore, this part of the query cannot be changed. Each grid can have as many Dataspies as the user defines and saves, and at least one of them will be set as default.
-
Dataspy—defines the additional filters, sort criteria, and displayed fields of a query. One default system Dataspy is always defined for each grid, as neither can stand alone. Users can modify the fields/filters/sorts in a Dataspy and save their own copy to run per user login account.
-
Grid Fields—defines a list of available fields that can be used to build the Dataspies (filterable, sortable, displayable fields)
-
Query Fields—defines the current list of displayed fields for a Dataspy. Includes the column widths and order in the displayed grid.
-
Fields—defines a field that can be filtered, displayed, or sorted in a grid/Dataspy
The following examples about queries are provided. These correspond to the given tables shown in the diagram on the next page.
-
BEWSGR—Base grid query definition from tables R5GRID and default Dataspy in R5DDDATASPY
-
BEWSDP—Dataspy definition from table R5DDDATASPY
-
BEWSGF—Available fields for a grid definition from table R5GRIDFIELD
-
BEWSDF—Fields definition from table R5DDFIELD
-
BEWSDE—Dataspy displayed field definitions from table R5QUERYFIELD