Documentation
Inspect datasets and find errors
Understand your report data with the Dataset Viewer: result sets, structure view, relationships, import and export.
On this page
Dataset Viewer
Generate the dataset with real request-page filters or load saved XML. Available views include the flat dataset, Dataset Structure, Labels, Information and XML Structure. Refresh or F5 retrieves the data again.
Flat result sets and relationships
The flat view expands nested DataItems into rows, repeating parent values in child rows. ∅ marks an absent value (NULL); an empty cell is an actual transmitted empty value. Toggle row metadata, wrapping, best-fit widths and sticky link columns to inspect counts, repetitions, values and formatting information.
Nested DataItems express parent-child relationships. Successive sibling DataItems form separate data branches: in the flat result, the previous branch's columns end and the next branch's columns become populated. Columns belonging to the other branch contain NULL. Row bands, parent context and highlighted link columns help you identify the originating path and the relationship responsible for repetition.
Sticky columns are derived from DataItemLink, sorting fields and key information. They keep parent and child keys visible while scrolling horizontally. Check those values first when repetitions are unexpected; incorrect keys or ordering point to an AL dataset issue.
Structure and saved datasets
Dataset Structure keeps the hierarchy in nested expandable tables. XML Structure shows the raw XML for technical checks. Use the flat view for the resulting rows and the structural views for DataItems and scopes.
The file menu loads and saves raw dataset XML and imports or exports flat dataset XML. Import validates the format and columns against the active report. Saved result sets enable reproducible layout tests without retrieving live data again. Anonymise business data before placing it in a repository.
ALRC: Show Dataset
Displays the actual dataset produced by Business Central as a flat result set and in its original DataItem hierarchy. Labels, technical information and XML structure are available as well.
When debugging, first check whether AL provides the values, row counts, links and formatting information you intended. If those are correct, focus on the layout. Otherwise, investigate the AL dataset.
Dataset or RDLC layout? Pinpoint compiler errors
First use Dataset Viewer to check values, rows, relationships and the DataItem structure. This helps you determine whether the cause is already in the AL dataset or whether you should investigate the layout. A correct dataset alone does not confirm that the RDLC layout compiles.
If Business Central reports a vague RequestMinimum failure for an RDLC layout, the extension can obtain the underlying compiler diagnostic with error text and position. This helps you fix the actual issue instead of reversing changes one by one, losing the designer's undo history whenever it closes due to the need of reloading the layout.
RDLC compiler diagnostics complement data inspection. They run when checking the RDLC layout, not simply when opening a dataset view. For further guidance, see Review reports with live data.