You can use reports to print or display information from a database. You can use a report to structure and summarize information and to print documents, such as invoices. For example, you can create a report that lists all customers and all orders that have been added by each customer. You can also create a report that is automatically filled with the relevant information for an invoice.
You can also use reports to process data without printing or displaying content. For example, you can use a report to automate updating all prices in an item list. It can be easier to create a report to process data instead of a codeunit to do the same processing because you can use:
- Request page functionality to select options
and filters for data items, which are available in a report but are
difficult to add to a codeunit.
- Report data items instead of writing code to
open tables and retrieve records.
- Data modeling, which is available when you
design reports.
The following sections describe the documentation that is available for reporting in Microsoft Dynamics NAV 2013.
RDLC Reports
To design a client report definition (RDLC) report, you design the data model with Report Dataset Designer and you design the layout with Visual Studio Report Designer.
To | See |
---|---|
Understand the difference between designing a data model for a report and designing the layout for a report. |
|
Understand the different types of reports. |
|
Learn how to design reports. |
|
Learn the system requirements for Microsoft Dynamics NAV 2013 reports. |
|
Upgrade a Microsoft Dynamics NAV 2009 report to a Microsoft Dynamics NAV 2013 report. |
|
Add a report to the ribbon in the RoleTailored client. |
|
Learn about the different ways to run a specific report. |
|
Learn about report triggers and when they are called during report processing. |
|
Learn about how to design request pages for reports. |
|
Step through detailed examples of creating reports |
|
Use Visual Studio Report Designer to design the layouts of reports |