Share This Post

NAV Updates

Dynamics NAV Reports Overview

Dynamics NAV Reports

You can use the Dynamics NAV reports to print or show the information from a database. You can use a report to structure and summarize information and print documents, such as invoices.

For example, you can create a report that lists all the customers and all the orders that have been included by each customer. You can also create the Dynamics Navision reports that is automatically filled with the relevant data for an invoice.

Dynamics NAV Reports

Dynamics NAV Reports

You can also use the reports to process information without printing or showing the content. For example, you can use the report to automate updating all the prices in an item list. It can be easier to create the report to process information instead of the code unit to do the same processing because you can use:

  • Request page functionality to choose the options and filters for information items, which are available in a report but are difficult to add to a code unit.
  • Report information items instead of writing the code to open tables and retrieve records.
  • Data modeling, which is available when you design the reports.

Creating Reports

Creating the Microsoft Dynamics NAV reports adds 2 primary tasks. First, you design the data model, by using the Report Dataset Designer.

The data model determines the data that is extracted or calculated from the Dynamics Navision database tables that can be used in a report.

After the data model has been designed, you design the visual layout of the report. There are 2 types of report layouts that you can create: client report definition report layouts and the Word report layouts. You can create the RDLC report layouts by using the Visual Studio Report Designer or the SQL Server Report Builder. You can create the Word report layouts by using the Microsoft Word 2013.

Dynamics NAV Report Design

A report object is composed of the following items:

  • Report dataset.
  • Report layout.
  • Request page.
  • Properties, triggers, and code. You design the report by 1st defining the dataset and then designing the visual layout.

Report Dataset

You use the Report Dataset Designer in the Microsoft Dynamics Navision Development Environment to define the dataset of a report. The dataset determines the information that is extracted or calculated from the Dynamics Navision database tables that can be used in a report. You build the report dataset by including the data items and columns. The data items and the columns correspond to fields in the table. When the report is run, each information item is iterated for all the records in the underlying table. Filters are applied and the dataset is created.

Report Layout

The visual layout determines the content and the format of a report when it is seen and printed. You build the layout of the Dynamics Navision reports by arranging the information items and columns and mentioning the general format, such as text font and size. The report that is seen, printed, or saved from the Dynamics Navision client must have the report layout. There are 2 types of report layouts: client report definition layouts and the Word layouts. layouts.

RDLC Report Layouts

Word Report Layouts

You can create the Word layouts by using Word. Word layouts are based on the Word document that adds the custom XML parts that represents the report dataset.

Types of Reports

List Reports

The list report contains a single information item that corresponds to the table that is listed. The table can be either the master table or the supplemental table. Each column contains a field from the table.

The information is printed from that table, instead of from other tables or calculated from other the tables. The name of a report is usually the name of the table followed by the word List. The following are examples of list reports:

  • Customer – List
  • Insurance – List
  • Vendor – List

Test Reports

The test report is the report that is printed from the journal table. Its purpose is to test each line in journal according to the same criteria that will be used for the posting.

You can use the test reports to find and fix the errors that exist before the lines are posted. This is useful because if an error is found during posting, processing stops and the error must be fixed before posting can be resumed.

The name of a report is usually the name of the corresponding journal page followed by the word Test. The following are examples of test reports:

  • General Journal – Test
  • Resource Journal – Test

Posting Reports

The posting report can be printed as part of the post and print option on the journal. This report is printed from a register and has the same name as that the register. It lists all the transactions, that is, the ledger entries, which have been posted into the register. The below are examples of posting Dynamics NAV reports:

  • G/L Register
  • Vendor Register

Transaction Reports

A transaction Dynamics NAV reports contain two data items. The first data item is a master table, and the second data item is the corresponding ledger table.

Usually, the transaction report lists all of the ledger entries for each record in a ledger table. There is the subtotal for each master table record and the grand total for all the tables that are printed.

This type of report is used to see all the transactions for a specific master record. The following are examples of transaction reports:

  • Trial Balance
  • Vendor – Trial Balance

Document Reports

Document reports differ from the other reports, in that, many of the fields are not shown in the columns.

The example of a document report is the invoice, where the header data is printed as if filling out the invoice document and this information is repeated at the top of each page.

No page contains the data from more than one header. The lines for an invoice are printed like the standard report in rows and the columns.

The lines correspond to the header on the same page, and the lines from other invoices are not shown on the same page. The following are examples of document reports:

  • Sales – Invoice
  • Purchase – Invoice

Processing-Only Reports

Processing-only reports only do the processing. They do not output or print a report. You use the Processing the Property of the report to create the report the non-printing report. You can use the request page and let the user filter the information before you run the report and start the processing.

Other Reports

The Reports are defined than other application objects because they are often customized for a specific client. However, most reports consist of a tabular list that has records listed horizontally and each field displaying in its own column. There is often the total to split the lines among various categories and subtotal the lines according to categories. The following are examples of other reports:

  • Vendor Item Catalog
  • Customer/Item Sales

Designing Reports

You design the report by 1st defining the data model and then designing the visual layout. You design the dataset for the reports in Report Dataset Designer of Microsoft Dynamics Navision Development Environment. When designing the layouts, there are 2 different types: RDLC report layouts and the Word report layouts.

You design the RDLC report layouts in the Visual Studio Report Designer. You design Word report layouts in Word. After you design the report’s dataset and the layout, you can create it available for running and printing in the Dynamics NAV client applications.

Share This Post

Leave a Reply

Notify of
Skip to toolbar