|
OpenRPT Product Guide |
|
|
OpenRPT Product Guide |
| 3.2. Retrieving Data | ||
|---|---|---|
 | 3. Modifying Query Sources |  |
Field objects are used to display dynamic data retrieved from a database. Typically, they are placed in the Detail section of a report definition. In this section, we will add a field object to handle our user email addresses.
To add a field object to the report definition, we select the icon from the toolbar and then click in the Detail section. We place the field object to the far-right of the section, lined up beneath the Email Address column heading, as shown in the following screen:
Now that we have placed the field object, we must define its properties. Double-clicking on the field object opens the Field Properties screen:
As you can see, we have filled in the following information:
We selected the detail query from the list of available query sources. This is the query whose SELECT statement includes the newly-added reference to the usr_email column.
Here we enter the name of the usr_email column—since this is the column whose data we need for the field object. A column must be referenced in the SELECT statement of the associated query source to successfully retrieve data from the database.
The preview shows us both the name assigned to the field object usr_email:detail and also the font choice. To make the font consistent with the other field objects in the report definition, we select the button and specify 8-pt bold Arial.
After we select the button, we see the field object has been updated in the report definition, as shown below:
We have now added the field object to the report definition—and aligned it correctly beneath the email address column headings. Once we save the report definition changes to the database, we will be ready to run the report and see the results.
To run the Users master list report from xTuple, select the option from the module menu. After selecting the button, the following report is generated:
As you can see, the user email addresses have been successfully added to the report.
| |  | |
| 3.1. Editing SQL Statements |  | 4. Total Fields |