Report elements

Some of the items specified in the report definition include the name of the report, whether any restrictions will be used to control the scope of the data included when the report is generated, and which tables data presented in the report will come from. Once you’ve defined necessary table relationships for a report, you can create the report. From the Resource Explorer, choose Reports for the current dictionary. To create a new report, click the New button in the Resource Explorer. The Report Definition window will open.

  1. Name the report.

Enter a report name. A report requires only one name. This is the name used in scripts when the report is run from a Dexterity application, and the name that will appear in the Report Destination window.

  1. Select a report series.

Series assignments allow you to group related reports in a Dexterity application using categories like Sales, Financial and Inventory. To ensure the consistent use of series in your application, it’s a good idea to select the series of the primary table as the report series.

If you’re creating a Dexterity application that integrates with Microsoft Dynamics GP, be sure you select the series your application is integrating with. This will allow security and pathname support to function properly in your application.

  1. Select a main table for the report.

The name of each table in the current dictionary is displayed in the list box below the Main Table field. From this list, select the table you want to use as the main table for the report. The main table is typically the table that contains the majority of information used by the report.

  1. Add additional tables to the report.

Click the Tables button to open the Report Table Relationships window. The report’s main table will be the only table listed in this window. The number 01 will appear to the left of the table name, denoting its status as the report’s main table.

Click New to add another table to the report. The Report Tables window will open. This window contains a list of all tables that have a relationship with the main table already defined using the Table Relationship Definition window. An asterisk appearing next to the table name denotes a one-to-many relationship. Select the desired table and click OK. Each table that is added to the report and is directly linked to the main table will be listed below the main table in the Report Table Relationships window, with a single dash to the left of the table name.

To add a table that is linked to a table other than the main table, select the secondary table’s name in the Report Table Relationships window and click New. Select the name of the table to be added and click OK. This table will appear in the Report Table Relationships window below the table that it is linked to, and will have two dashes to the left of its name.

The following illustration of the Report Table Relationships window shows the dashes that denote levels of linking.


You can have only one one-to-many relationship for each table used for the report. For example, if the Customers table is related to the Address, Invoice and Shipping tables, only one of the relationships can be one-to-many. The other relationships must be one-to-one.

Once you have added all the necessary additional tables, click Close to close the Report Table Relationships window.

  1. Set the maximum number of records for the report.

Use the Max Records field to restrict the number of records that will be printed on the report. The default value for this field is 0, which indicates that all records will be printed.

If you enter the number 10 in the Max Records field, for example, only the first 10 records in the report will be printed, unless a restriction has been created to specify another number. Any limit set using a restriction overrides the limit set using the Max Records field.

You may want to enter a relatively small number while you’re creating the report, so that test reports will be generated more quickly. Be sure to change the number to 0 or another appropriate number when you are finished testing.

What is an appropriate number depends upon the type of report and how it will be used. For example, you could generate a report that lists all sales statistics by salesperson. If the user will only want to view the top ten salespersons, you could set the Max Records field to 10.

Documentation Feedback