Skip to main content

Building a Flat Data Grid

A Flat Data Grid is a tabular report: rows and columns, with grouping, sorting, filtering, and totals. Use it when people need to see detailed rows or export raw data to Excel.
This page is part of the Report Designer guide. For choosing fields and building formulas, see Fields and Calculated Fields.

Build it

1

Create the report

On the landing page, click Create New Report and choose Flat Data Grid.
2

Choose your projects

Select one or more project snapshots. You can combine snapshots from several projects.
3

Add columns

Add columns one of two ways:
  • Quick-Add buttons add a whole category at once: + Cost, + Resources, + Time-phase, + WBS Structure.
  • Browse by category and check individual columns.
Added columns appear in the Selected Columns panel.
4

Arrange columns

In the Selected Columns panel, drag columns to reorder them. For each column you can:
  • Click the gear icon to Edit caption (change the display name; the data is unchanged).
  • Click the undo icon to Reset caption back to the default.
  • Click the X icon to Remove column.
5

Set display options

Open Display Settings and set the toggles (see the table below).
6

Add Quality Check columns (optional)

Add Yes/No columns that check whether a field is empty or missing, useful for data-quality audits. See Quality Check columns.
7

Add a header, then save

Add a title, subtitle, and description, then click Save.
Flat Data Grid configuration: Selected Columns panel, Quick-Add buttons, and Display Settings

Display settings

SettingWhat it doesDefault
Alternating RowsZebra striping for readabilityOn
Word WrapWrap long cell text instead of cutting it offOff
Filter RowA row of search boxes under the column headersOn
Column FixingLet users pin columns to the left or right edgeOff
Group Row PrefixShow the field name before the value in grouped rows (for example, “WBS Level 1: value”)Off
Summary FooterShow the Total row at the bottomOn

Fiscal Year prefix

Dash360 detects whether your selected projects use fiscal or calendar years. When all selected projects are the same, the prefix is applied automatically and an information row tells you so. When you mix fiscal-year and calendar-year projects, a Show Fiscal Year Prefix toggle appears so you can decide.

Totals and summaries

  • The Summary Footer toggle controls the grand-total row at the bottom.
  • Column totals appear for numeric cost columns the report displays (for example, Item Cost, Contingency, Unit Cost, Units).
  • Calculated fields can also produce totals. See Fields and Calculated Fields.

Quality Check columns

Quality Check columns turn a field into a simple Yes/No answer to “does this row have a value here?”
  • Open the Quality Check Columns section and pick the fields to check.
  • Each one becomes a column captioned QC: {Field} by default; you can edit the caption.
  • Use Clear All QC Columns to remove them all at once.
These are ideal for completeness audits, for example “which work packages are missing a Basis of Estimate.” Quality Check columns adding Yes/No completeness columns

Performance: apply filters early

A Flat Data Grid runs entirely on the server (the server does the paging, sorting, filtering, and totals, then sends back only what the grid needs). The single biggest thing you can do for responsiveness is reduce the number of rows the report has to work with:
Filter first, then explore. Before you sort, group, or scroll a large report, apply filters (project, WBS, Work Package, Cost Class, Resource Type) so the server works with fewer rows. A report narrowed to one WBS branch responds far faster than the whole project.
  • Select only the projects you need. Every extra snapshot adds rows.
  • Add only the columns you need. Fewer columns means less data per row.
  • Group and expand on demand rather than expanding everything at once on a huge dataset.
  • Results are cached for up to 30 minutes, so re-running the same report with the same filters is fast. Changing filters or projects runs a fresh query.

Pitfalls to avoid

  • Too many projects or no filters on a large project. The grid still works, but it will feel slow. Narrow the scope first.
  • Turning off Summary Footer when users expect totals. If users rely on the grand total, leave it on.
  • Renaming a column caption and assuming the underlying field changed. Captions are display-only; calculated fields and exports still use the real field name.
  • Expecting a saved view to remember filters. Views remember layout (columns, order, grouping, sorting), not filters. See Report Viewer.

Where to go next

Building a Pivot Grid

Cross-tab analysis with drag-and-drop zones.

Why Your Data Might Be Wrong

Snapshots, filters, permissions, and caching.