Designing, Running, and Printing Reports
You design the dataset for reports in Microsoft Dynamics NAV Report Dataset Designer. You design the layout for reports in Visual Studio Report Designer. After you design reports, you can make then available in client applications. For example, you can add a report to the Report tab of a page. When you preview a report from a client computer, the report is displayed using Report Viewer.
The following table describes where to find information about how to design, run, and print reports.
| To | See |
|---|---|
Learn about how to use the designers to create reports. |
How to: Integrate Report Dataset Designer and Visual Studio Report Designer |
Learn how to add a report to a client page. |
|
Learn about how to run reports from Object Designer, a client, or at a command prompt. |
|
Learn about printer settings for reports. |
|
Walk through examples of designing reports that use the CRONUS International Ltd. demonstration database |
Report Viewer
The ReportViewer controls included with Visual Studio 2012 and Visual Studio 2013 allow reports to be embedded in Microsoft Dynamics NAV client applications. The ReportViewer controls are installed automatically on the following:
Client computer, for viewing reports from the Microsoft Dynamics NAV client.
Microsoft Dynamics NAV Server, for using the SAVEASEXCEL and SAVEASPDF functions.
Computer running the development environment, for compiling reports.
The ReportViewer controls included with Visual Studio 2012 and Visual Studio 2013 prevent code expressions in hidden items on a report from being evaluated. We recommend that you eliminate code expressions from hidden items on reports.
In Microsoft Dynamics NAV 2009, when you redesigned Classic reports as client report definition (RDLC) reports, in some cases, you may have created hidden text boxes in the body of a report so that in the RDLC layout, you could reference that report item in the header or footer of the report. In Microsoft Dynamics NAV 2013 R2 you do not have to create hidden text boxes in order to reference an item in a header or footer because the RDLC version allows data-bound fields in headers and footers. Additionally, if the hidden text boxes that you added had code expressions, then they may not be evaluated by the ReportViewer controls that are used in Microsoft Dynamics NAV 2013 R2. We recommend that you move these data-bound fields out of the hidden items. For example, you may be able to move the code expression from the hidden text box to the Visibility property of the text box. For more information, see How to: Print Report Header Information on Multiple Pages.