Business Central RDLC Grouping & Expressions: Complete Guide

Dynexal • Beginner to Intermediate • 14 min read

Grouping and expressions are two of the most useful RDLC skills for building professional Microsoft Dynamics 365 Business Central reports. In this practical guide, you will learn how to create groups, calculate totals, use expressions such as Sum() and IIF(), control expression scope, format values, add group headers and footers, and troubleshoot common Report Builder problems.

What you will learn: row groups, parent and child groups, group totals, expressions, IIF, formatting, scope, page breaks, conditional formatting, duplicate rows and troubleshooting.

What are RDLC groups?

An RDLC group organizes rows in a tablix according to a field or expression. For example, a sales report can group sales lines by salesperson, customer, posting date or item category. Grouping is performed in the RDLC layout; the AL report dataset supplies the fields that the layout can use.

Business Central reports have a dataset and a visual layout. Microsoft describes RDLC as a layout type intended for advanced, pixel-precise reporting scenarios. Microsoft Learn: Working with RDLC Layouts

Simple example: group sales by customer

Suppose your dataset exposes CustomerNo, CustomerName, DocumentNo and Amount. In Report Builder, add a parent row group based on CustomerNo.

Open the RDLC layout in Report Builder.
Select the tablix containing your detail rows.
In Row Groups, choose Add Group → Parent Group.
Select CustomerNo as the group expression.
Choose whether to add a group header.
Place customer information in the group header and transaction fields in the detail row.

=Fields!CustomerNo.Value

The expression above identifies the current customer's value for the group.

Group header vs detail row

A group header is a good place for values that should appear once per group, such as Customer No. and Customer Name. The detail row should contain values that repeat for each transaction or line.

Group Header
Customer: =Fields!CustomerName.Value

Detail
Document: =Fields!DocumentNo.Value
Amount:   =Fields!Amount.Value

Tip: if a customer name is repeated on every transaction row, move it into the group header when the report design calls for a cleaner grouped layout.

Group totals with Sum()

The most common RDLC aggregate is Sum(). A group footer can show the total for the current group:

=Sum(Fields!Amount.Value)

When the textbox is inside a group footer, the aggregate normally evaluates over the rows in that group. You can also explicitly specify scope when you need to control which group or dataset the aggregate uses.

Understanding aggregate scope

Scope is one of the most important RDLC concepts. An aggregate can be evaluated against the current group, a parent group or the entire dataset depending on where it is placed and which scope is specified.

=Sum(Fields!Amount.Value, "CustomerGroup")

Here, CustomerGroup represents the name of the relevant RDLC group. The exact group name comes from your layout. If totals appear too large or repeat unexpectedly, inspect the aggregate scope first.

Common mistake: using a dataset-wide aggregate when you actually need a group total. Always verify the scope of totals with at least two groups and several detail records.

Grand total

A report-level total can be created with an aggregate over the dataset:

=Sum(Fields!Amount.Value, "DataSet_Result")

The dataset name depends on your RDLC layout. Do not copy the example name blindly—select the correct dataset/group scope from your report.

Conditional expressions with IIF()

IIF() is useful when a report needs to display different text or formatting based on a condition.

=IIF(Fields!Amount.Value > 10000, "High Value", "Standard")

For example, you can display a label based on an amount, status or quantity. Keep conditions readable; move complicated business rules into AL when they become difficult to maintain in the layout.

Conditional formatting

Expressions can also be used in properties such as font color, background color or visibility. For example, a value can be highlighted when an amount exceeds a threshold.

=IIF(Fields!Amount.Value > 10000, "Red", "Black")

For production reports, use conditional formatting sparingly. A consistent visual hierarchy is usually more useful than highlighting every value.

Formatting numbers and dates

RDLC provides standard formatting functions. For a two-decimal numeric display:

=Format(Fields!Amount.Value, "N2")

For a date:

=Format(Fields!PostingDate.Value, "dd-MMM-yyyy")

Be mindful of localization and currency requirements. If the report must respect company or user-specific formatting, verify the output in the actual Business Central environment.

Parent and child groups

Nested groups are useful for reports such as:

Salesperson → Customer → Document
Category → Item → Transaction
Year → Month → Day

Create the outer group first, then add a child group beneath it. Each level can have its own header, footer and aggregate calculations.

Salesperson Group
  Customer Group
    Detail Rows

Keep nesting limited to what the reader actually needs. Deep group hierarchies are harder to troubleshoot and can make pagination complicated.

Group footer and subtotal pattern

A clean invoice or sales report often follows this pattern:

Customer Header
    Document / Line Details
Customer Footer
    Customer Total

Next Customer...

Report Footer
    Grand Total

This structure makes it easier for users to understand where each subtotal ends and where the final report total begins.

Page breaks for groups

If each customer or document must start on a new page, configure the relevant group's page-break settings in Report Builder. Test the output with both short and long groups because page breaks can interact with headers, footers and keep-together settings.

Avoid forcing a page break after every small group unless the business requirement really needs it; otherwise the PDF can contain many pages with large amounts of unused space.

Visibility and drill-down

Group rows can be hidden and shown through visibility expressions or interactive drill-down patterns. This is useful when a report should initially show summaries and let users expand details.

=IIF(Fields!Status.Value = "Closed", True, False)

Use hidden rows carefully and test exported PDFs because interactive behavior is most useful in supported report viewing scenarios and may not provide the same experience in every output format.

Why totals can be duplicated

A frequent Business Central RDLC problem is an unexpectedly high total. The cause is often the AL dataset rather than the RDLC expression.

For example, if a parent record is repeated because of nested dataitems, an expression such as Sum() may add the same parent amount multiple times.

Inspect the AL dataset.
Check the number of rows returned.
Look for nested dataitems that repeat parent values.
Confirm whether the value being summed belongs to the detail row or parent row.
Only then change the RDLC expression.

Key lesson: an RDLC total can only be correct if the underlying dataset has the correct row structure.

RDLC expressions vs AL logic

Use simple presentation logic in RDLC: formatting, labels, visibility and straightforward calculations. Use AL for important business rules, data preparation and reusable logic.

This separation makes reports easier to test and reduces the risk of hiding critical business behavior inside a layout file.

Testing a grouped RDLC report

Test one group with a few detail records.
Test at least two groups.
Test a group with many detail rows.
Test filters that return no records.
Verify every subtotal.
Verify the grand total independently.
Export to PDF and check page breaks and widths.
Test the report with realistic production-sized data.

Common RDLC errors and fixes

“The textbox expression is invalid”

Check field names, parentheses, quotation marks and the selected dataset scope.

Total is too high

Inspect dataset duplication and aggregate scope before changing the formula.

Group does not appear

Confirm that the group was added to the correct tablix and that the group expression references a dataset field.

Blank page appears

Check body width, page width, margins and objects extending beyond the printable area.

Field is missing

Make sure the value is exposed as an AL report dataset column and refresh the dataset in the RDLC designer.

RDLC grouping best practices

Design the AL dataset before building complicated groups.
Use meaningful dataset column names.
Keep group hierarchy as simple as possible.
Use explicit aggregate scope when it improves clarity.
Keep complex business rules in AL.
Test totals with multiple groups and filters.
Always inspect the exported PDF.
Keep the layout maintainable for the next developer.

RDLC Grouping vs simple RDLC layout

A simple RDLC layout is enough when the report is a flat list. Grouping becomes valuable when users need subtotals, sections, summaries or hierarchical presentation. The goal is not to add groups everywhere; it is to make the report easier to read and reconcile.

Related Dynexal tutorials

Frequently Asked Questions

Where are RDLC groups created?

Groups are created in the tablix Row Groups or Column Groups areas in Report Builder.

Can I calculate a subtotal with Sum()?

Yes. Sum() is commonly used for group and report totals, but the scope must match the required level.

Should business logic be written in RDLC?

Prefer AL for important business rules. Keep RDLC expressions focused on presentation and simple calculations.

Why does my RDLC total duplicate?

Check both aggregate scope and the AL dataset for duplicated parent rows caused by nested dataitems.

Which tool can edit RDLC layouts?

Microsoft SQL Server Report Builder and the Microsoft RDLC Report Designer can be used for RDLC/RDL layouts. Microsoft notes that Report Builder works with .rdl files, while Business Central layouts can use .rdlc.

Next step: Build a small grouped sales report, verify its dataset, then add one group subtotal and one grand total before moving to more advanced expressions.

← Explore all Business Central tutorials