Report object
Reports are used to print or display information from a database. You can use a report to structure and summarize information, and to print documents, such as sales quotes and invoices.
The report object is typically used for one of the following three different scenarios:
- analytical reports, where the output is meant for online consumption of data.
- document reports, where the output is meant for print.
- processing-only reports, where there's no output. In this case, the report object is typically used with a request page to let the user set filters/options for the operation.
Creating a report consists of two primary tasks; the first task is to create the underlying data model, and for analytical and document reports, the second task is to define the visual layout that displays the data. The report object defines the underlying data model and specifies, which database tables and fields to pull data from. When the report is run, that data is displayed in a specified layout; the visual layout, which determines the content and format of a report when it's viewed and printed.
For more information about defining database tables and fields, see Defining a Report Dataset. For more information about the Report data type, see Report Data Type.
If you want to modify an existing report, for example, add new columns, add to the request page, or add a new layout, you can create a report extension instead. For more information, see Report Extension Object.
Tip
It is possible to use a query object as the data source for a report. This can in many cases improve the performance of data retrieval when running the report.
Report syntax
A report object consists of properties, a dataset section, and optionally sections for request page, layouts, and code. The order in which the sections appear matters. The following example illustrates the ordering:
report ObjectId ReportName
{
// report properties such as
UsageCategory = ReportsAndAnalysis;
ApplicationArea = All;
dataset {}
// requestpage section is optional
requestpage {}
// rendering section is optional, but recommended for reports that have a layout
rendering {}
// optionally, add AL code here
}
Snippet support
Typing the shortcut treport will create the basic layout for a report object when using the AL Language extension for Microsoft Dynamics 365 Business Central in Visual Studio Code.
Tip
Use Ctrl+Space to trigger IntelliSense and get assistance on code completion, parameter info, quick info, and member lists. For more information about snippets, see Syntax and snippets.
Report properties
You can control the way the AL runtime and client work on the report by setting properties on the report object. Some popular properties are:
- AdditionalSearchTerms - helps users when searching for the report in Tell Me search.
- Caption - specifies the report title as shown on request pages, Tell-me search, report/role explorer, and when users bookmark the report to their role centers.
- UsageCategory - determines how the report is shown in report/role explorer.
- AllowScheduling - allows the report to be run in the background.
- DataAccessIntent - allows the AL runtime to read data from a secondary database, if present.
For a list of all properties that you can set on the report object, see the AL language reference article Report, Report Fields, and Report Extension Properties.
Report layouts
You build the layout of a report by arranging data items and columns, and specifying the general format, such as text font and size. There are three types of report layouts; client report definition, also called RDL layouts, Word layouts, and Excel layouts. RDL layouts are defined in Visual Studio Report Designer or Microsoft SQL Server Reporting Services Report Builder. Word layouts are created using Word and are based on a Word document that includes a custom XML part representing the report dataset. Excel layouts are created in Excel based on the report dataset, utilizing the Excel capabilities such as sliders, diagrams, charts, pivot tables, and PowerQuery. One report can contain multiple report layout definitions. For more information, see Defining Multiple Report Layouts.
In the following, you can read about properties of the different layout types.
| Layout type | Properties |
|---|---|
| Excel | No-code layout experience for end-users. Primary layout type for analytical reports. Does not support printing from the request page. |
| RDL | Pro-developer layout experience (not for end-users.) Mostly needed for document reports. Use this layout type when you need pixel-perfect outputs for printing. Supports printing from the request page. |
| Word | Low-code layout experience. Some expert end-users can work with XML and tags. Mostly needed for document reports. Supports printing from the request page. |
Report labels
Report labels are used by report layouts as, for example, the heading for a field in a table, the title for a chart, or the title for the report itself.
For texts that are present as captions on table fields in dataset columns, use the IncludeCaption property to include them in the dataset. For more information, see IncludeCaption property.
You define report labels for static texts that are not present as captions in dataset columns inside the labels control of a report object, as shown in the following code sample.
labels
{
LabelName1 = 'Label Text1', Comment='Foo', MaxLength=999, Locked=true;
LabelName2 = 'Label Text2', Comment='Foo', Locked=false;
}
All of the different layout types (Excel, Word, or RDL) support using label data. For more information, see:
For a code example on how to use report labels for an RDL layout, see Walkthrough: Designing a Report from Multiple Tables.
For more information about labels, see Working with labels.
Report example
The following example is a report that prints the list of customers. The report object defines a dataset of columns from the Customer table. This example defines a report that uses an RDL report layout. For more information about creating an RDL report layout, see Creating an RDL Layout Report. For more information on creating a report that uses Word Layout, see Creating a Word Layout Report. For information about creating an Excel layout, see Creating an Excel Layout Report.
report 50103 "Customer List"
{
Caption = 'Customer List';
AdditionalSearchTerms = 'Sales, Sold';
UsageCategory = ReportsAndAnalysis;
AllowScheduling = true;
DataAccessIntent = ReadOnly;
dataset
{
dataitem(Customer;Customer)
{
RequestFilterFields="No.","Search Name","Customer Posting Group";
column(CompanyName;CompanyName)
{
}
column(CurrReport_PageNo;Customer."no.")
{
}
column(Customer_TableCaption_CustFilter;TableCaption + ': ' + CustFilter)
{
}
column(CustFilter;CustFilter)
{
}
column(Customer_No;"No.")
{
}
column(Customer_Customer_Posting_Group;"Customer Posting Group")
{
}
column(Customer_Customer_Disc_Group;"Customer Disc. Group")
{
}
column(Customer_Invoice_Disc_Code;"Invoice Disc. Code")
{
}
column(Customer_Customer_Price_Group;"Customer Price Group")
{
}
column(Customer_Fin_Charge_Terms_Code;"Fin. Charge Terms Code")
{
}
column(Customer_Payment_Terms_Code;"Payment Terms Code")
{
}
column(Customer_Salesperson_Code;"Salesperson Code")
{
}
column(Customer_Currency_Code;"Currency Code")
{
}
column(Customer_Credit_Limit_LCY;"Credit Limit (LCY)")
{
DecimalPlaces=0:0;
}
column(Customer_Balance_LCY;"Balance (LCY)")
{
}
column(CustAddr_1;CustAddr[1])
{
}
column(CustAddr_2;CustAddr[2])
{
}
column(CustAddr_3;CustAddr[3])
{
}
column(CustAddr_4;CustAddr[4])
{
}
column(CustAddr_5;CustAddr[5])
{
}
column(Customer_Contact;Contact)
{
}
column(Customer_Phone_No;"Phone No.")
{
}
column(CustAddr_6;CustAddr[6])
{
}
column(CustAddr_7;CustAddr[7])
{
}
column(Customer_ListCaption;Customer_ListCaptionLbl)
{
}
column(CurrReport_PageNoCaption;CurrReport_PageNoCaptionLbl)
{
}
column(Customer_NoCaption;FieldCaption("No."))
{
}
column(Customer_Customer_Posting_GroupCaption;Customer_Customer_Posting_GroupCaptionLbl)
{
}
column(Customer_Customer_Disc_GroupCaption;Customer_Customer_Disc_GroupCaptionLbl)
{
}
column(Customer_Invoice_Disc_CodeCaption;Customer_Invoice_Disc_CodeCaptionLbl)
{
}
column(Customer_Customer_Price_GroupCaption;Customer_Customer_Price_GroupCaptionLbl)
{
}
column(Customer_Fin_Charge_Terms_CodeCaption;FieldCaption("Fin. Charge Terms Code"))
{
}
column(Customer_Payment_Terms_CodeCaption;Customer_Payment_Terms_CodeCaptionLbl)
{
}
column(Customer_Salesperson_CodeCaption;FieldCaption("Salesperson Code"))
{
}
column(Customer_Currency_CodeCaption;Customer_Currency_CodeCaptionLbl)
{
}
column(Customer_Credit_Limit_LCYCaption;FieldCaption("Credit Limit (LCY)"))
{
}
column(Customer_Balance_LCYCaption;FieldCaption("Balance (LCY)"))
{
}
column(Customer_ContactCaption;FieldCaption(Contact))
{
}
column(Customer_Phone_NoCaption;FieldCaption("Phone No."))
{
}
column(Total_LCY_Caption;Total_LCY_CaptionLbl)
{
}
trigger OnAfterGetRecord();
begin
CalcFields("Balance (LCY)");
FormatAddr.FormatAddr(
CustAddr,Name,"Name 2",'',Address,"Address 2",
City,"Post Code",County,"Country/Region Code");
end;
}
}
requestpage
{
SaveValues = true;
// These properties control the title and content of the teaching tip.
AboutTitle = 'Awesome report';
AboutText = 'This is an awesome report. Use it to be awesome';
// Use the multi-language versions AboutTitleML and AboutTextML if you need that.
// This property defines the help page for this report.
// Remember to also set contextSensitiveHelpUrl in the app.json
ContextSensitiveHelpPage = 'my-feature.html';
layout
{
}
actions
{
}
}
labels
{
Label1 = 'Label Text', Comment = 'Foo', MaxLength = 999, Locked = true;
}
rendering
{
layout(LayoutExcelPivot)
{
Type = Excel;
Caption = 'Customer list (analyze)';
Summary = 'Customer list for analysis in Excel';
LayoutFile = 'CustomerListExcel.xlsx';
}
layout(CustomerListPrintLayout)
{
Type = RDLC;
Caption = 'Customer list (print)';
Summary = 'Customer list in print layout';
LayoutFile = 'CustomerListRDL.rdl';
}
}
trigger OnPreReport();
var
CaptionManagement : Codeunit 42;
begin
CustFilter := CaptionManagement.GetRecordFiltersWithCaptions(Customer);
end;
var
FormatAddr : Codeunit 365;
CustFilter : Text;
CustAddr : ARRAY [8] OF Text[50];
Customer_ListCaptionLbl : Label 'Customer - List';
CurrReport_PageNoCaptionLbl : Label 'Page';
Customer_Customer_Posting_GroupCaptionLbl : Label 'Customer Posting Group';
Customer_Customer_Disc_GroupCaptionLbl : Label 'Cust./Item Disc. Gr.';
Customer_Invoice_Disc_CodeCaptionLbl : Label 'Invoice Disc. Code';
Customer_Customer_Price_GroupCaptionLbl : Label 'Price Group Code';
Customer_Payment_Terms_CodeCaptionLbl : Label 'Payment Terms Code';
Customer_Currency_CodeCaptionLbl : Label 'Currency Code';
Total_LCY_CaptionLbl : Label 'Total (LCY)';
}
Tip
From the Business Central client, you can export report results as raw data to a Microsoft Excel file. The file contains all columns of the dataset, but without the layout applied. Use the file to help validate that the report returns the expected data, and to ensure that the report layout controls match the dataset value types. To export a report dataset to Excel, run the report and select the Send to > Microsoft Excel Document (data only) on the request page. For more information, see Working with Reports - Send to Excel.
Schedule reports
It's possible to schedule a report to run at your desired date and time by using AllowScheduling property. By setting the property to true, you'll get the Schedule action button to set the date and time for your report. To learn more about scheduling a report, see AllowScheduling Property and Schedule a report.
Report limits
The Business Central platform has built-in limits to protect the stability of the system from a single report consuming too many resources. Examples of limits are:
- The maximum number of rows that can be processed in a report.
- The maximum number of documents that can be merged in a report using a Word layout.
- The maximum execution time that it can take to generate a report.
If any of these limits are reached, then the report is cancelled. If a report gets cancelled, you get an event in telemetry. For more information, see Telemetry for report generation cancelled.
For more information on report limits in Business Central and how they are configured in the online service, see Report limits in Business Central.
For more information on how to configure report limits in Business Central on-premises environments, see Server settings for reports.
Note
For Excel layouts and the ability to get report data in Excel without a layout, you also need to take Excel limits into consideration. Learn more in Excel limits.
Related information
Report Extension Object
Using request pages with reports
Report datatype (AL reference)
Report Properties
How users can schedule a report
AllowScheduling Property
IncludeCaption property
Defining a Report Dataset
Request Pages
Adding Help Links from Reports
Creating an Excel Layout Report
Creating an RDL Layout Report
Creating a Word Layout Report