Reports > View queries 

This function makes it possible to view the results of the requests parameterized by the requests creation function, or the SQL requests function and executed previously, or to re-execute them by modifying the execution criteria before viewing them. From the results of this request, presented at its most detailed level, it is possible to zoom onto the linked objects, to regroup the lines interrogated as a function of the field breaks defined in the request, to trigger the display of a graph, or export the result to a spreadsheet.

    Prerequisite

    SEEREFERTTO Refer to documentation Implementation

    Screen management

    Entry screen

    Presentation

    If the function is opened without having selected a specific request, a preliminary entry screen makes it possible to choose it.

    A screen containing a single tab opens, in which there is a group of columns containing the data arising from the request interrogation (they are stored in the ALISTER table).

    In the header there is the information relating to the last request execution.

    The execution can be carried out by thekey, which makes it possible to trigger a refresh in a generic fashion (it is also used for the left lists), or using File/Refresh. It can also be carried out by entering the criteria with the help of the appropriate button.

    In order for the execution to happen, it is necessary that the user be authorized (this makes it possible, when the requests are shared, to only authorize enquiries on requests already carried out).

    In the table that follows, the columns coming from the query are found with detail lines. By positioning the cursor on a line, it is possible by right click, to zoom onto the records relative to the information whose keys are displayed on the line. For instance, if there is a request giving by country, then by customer, then by order line, the detail of the products and the corresponding quantities, it is possible to zoom onto the customer record corresponding to the customer on the line, on the country record, on the product... (but not onto the order if the order number does not appear in the line).

    It is also possible to navigate from page to page with the radio buttons situated in the top menu line, and using the buttons at the bottom of the page described below.

    Close

     

    Fields

    The following fields are present on this tab :

    Block number 1

    This code is used to identify a request.

    • field DES

    Title associated to the previous code.

    • Last generation (field DAT)

    It indicates the date and time of the last generation. These fields are empty if no generation has been made yet.

    • field TIM

     

    • field USR

    It defines the code of the last user who executed the request (when the request is shared, the user can be different from the current user).

    Block number 2

    • Time (field TEMPO)

    It specifies the execution time (in seconds) necessary to the last request execution.

    When a long execution is in progress, the number of seconds elapsed is displayed as the execution progresses.

    • Level (field NIVP)

    This field defines the current level of detail and the maximum level number (the maximum level is used at the start: 4/4 is displayed if, for instance, the maximum level number is 4). The level management buttons make it possible to then navigate from one level to another.

    • Lines (field LIG)

    It specifies the number of lines created by the request when it was last executed.

    When a long execution is in progress, the number of lines being found is displayed as the execution progresses.

    • Page (field PAGP)

    It indicates a page number and the maximum number of pages on which the request is displayed (this depends on the maximum number of lines displayed in the screen, parameterized in the request definition).

    Table

    Close

     

    Functions accessed by right click on the grid

    Base Product Management

    By right click on the lines, a group of zooms can be obtained, depending on the context linked to the request, to perform a tunnel up to the data related to the request.

    Standard object management
    Standard object management
    Standard object management
    Standard object management
    Standard object management
    Standard object management
    Standard object management
    Standard object management

     

    Fermer

     

    Specific Buttons

    It makes it possible to change the query.

    It makes it possible to re-launch the execution (it is equivalent to a refresh).

    It makes it possible to modify the query criteria. By validating these criteria, the request is executed, then its result is displayed. 

    It makes it possible, having navigated from a given level to a less detailed level using the Level - button, to carry out the reverse operation (moving to a level with greater detail). It should be noted that: when navigating in this way from level to level, the current line is used to determine the current page. For instance, let us assume that a query has created 10,000 lines, paginated by 100 (therefore 100 pages are in the query). If the user returns to the most detailed zoom level, and then positions on the 15th line (no pagination is required, because at this level only one line by aggregate is displayed), the fact of re-descending by changing the level until the level of detail positions the user on the first line of detail associated with the 15th value of the first criterion (in this way the user finds themselves directly in page 45 of the query, the pagination being carried out automatically).
     

    It makes it possible to return to a less detailed level, by aggregating the lines on the last criterion for which the Group indicator is equal to Yes, then on the next criteria if the operation is repeated. Only the information that remains valid still appears again in the table, the fields for which totals are requested appear with totals. This navigation by level is not possible on requests made with the SQL requester.

    Let us illustrate this function with an instance coming from commercial management. If a request is asked for:

    • by country code (this field has the attribute Group equal to Yes)
    • then displaying the country name (in group 1)
    • then by ordering customer coming from the order header (this field has the attribute Group equal to Yes)
    • then displaying the customer name (in group 2)
    • then by product extracted from the order line (this field has the attribute Group equal to Yes)
    • by displaying the order number, a quantity and a price extracted from the order line (in group 4, the last two fields being totalled)

    The following successive displays are obtained:

    • firstly, the line detail, the displayed level being 4/4
    • by moving up a level, a line by product and by customer is displayed. The country code, country name, customer code, customer name and product fields are still displayed. The order number is empty, the quantity and price information being totalled for all the order lines concerning the product and the customer. The level displayed will be equal to 3/4.
    • by moving up another level, a line by customer is displayed. The country code, country name, customer code and customer name fields are still displayed. The product and order number fields are no longer significant and are therefore no longer displayed. The totals concern all the order lines for the customer, the level displayed being equal to 2/4.
    • by moving up another level, a line by country is displayed. Only the country code and country name fields remain displayed (and of course the price and quantity totals, which are now equal to the total by country). The level displayed is now 1/4. 

    It makes it possible to create, on a client workstation, a file in the csv format (usable by a spreadsheet), It is simply necessary to give the file path (without specifying the network path, the client workstation being used by default). It is also possible to create the file on a network server (provided that this server includes an Adonix run-time), thanks to the server@path syntax. The format of the created file is defined by the values of the RQTFMT and RQTSEP parameters.

    Error messages

    In addition to the generic error messages, the following messages can appear during the entry :

    Write error

    The attempt to create a file in the csv format has failed.

    Tables used

    SEEREFERTTO Refer to documentation Implementation