Unlike an Advanced Report (which lists rows from a single data source) or a Matrix Report (which summarizes a single data source across row and column groupings), a Workday Composite Report pulls aggregated columns from multiple subreports—often across different data sources such as Journal Lines, Budget Lines, and Headcount—and aligns them on a shared Control Field Column and Outline Structure. When a composite report shows blank data columns, refuses to select a subreport, fails to pass runtime filters, or throws a join exception, the fault lies in the contract between the composite report definition and its underlying subreports.

This guide explains the five failure points in Workday composite reports and how to diagnose and repair them using Workday's built-in validation tools.

When you add a Data Column in Edit Custom Report (secured by Custom Report Creation and Manage: All Custom Reports in the System functional area) and search the Sub Report Name prompt, Workday filters out subreports that violate composite reporting rules:

  • Unsupported summarization types: Workday does not allow you to select matrix or trending subreports that use Percentile summarization fields or Text-based Count Distinct summarization fields.
  • Prism data source requirement: If a composite report uses a Prism data source, that Prism data source must include at least 1 Instance field so Workday has a business object key to join on.
  • Orphaned subreports blocking deletion: If you try to delete an old subreport or summarization field that was once attached to a composite report, Workday blocks the deletion until you run the Clean Up Custom Report task (from the composite report's related actions → Report Definition) to disassociate unused custom subreports and their summarization fields.

2. Map Fields For Join exceptions and Control Field mismatches

Every data column in a composite report must join its subreport's grouping dimension back to the composite report's Control Field Column (for example, Ledger Account, Cost Center, or Supervisory Organization).

  • How Map Fields For Join works: The available Join Field options in a data column correspond to the business object used on the Control Field Column. Two subreports can group by differently named fields (such as Ledger Account and Ledger Account by Name) and still join cleanly on the same composite report as long as both fields resolve to the same Ledger Account related business object.
  • Why rows show zero or fail to align: If a matrix subreport groups by a text field or a calculated field that returns text instead of the Instance business object, Workday cannot join it to the Control Field Column's business object. Promote the related Instance field to the subreport's Primary Business Object using a Lookup Related Value (LRV) calculated field and group the matrix subreport by that Instance field.
  • Running Validate Composite Reports: From the composite report's related actions menu, select Custom Report → Validate (or run the Validate Composite Reports report directly). Workday flags Anomalies, Exceptions, and Warnings across your columns and cells. Where Workday displays a Fix button, clicking Fix automatically repairs common metadata corruptions—such as removing duplicate references to a Web Service ID or repairing join exceptions in the Map Fields For Join grid.

3. Why subreports ignore runtime prompts (Prompt Sets and Map Sub Report Prompts)

When subreports use different report data sources (for example, Journal Lines for Financial Reporting in Column B and Workday Standard Budget Lines in Column C), their built-in data source prompts and filter prompts are separate objects. If a user enters Company and Time Period when launching the composite report, a subreport will ignore those values or fail unless its prompts are mapped:

  1. Create or select a Prompt Set: Use a Workday-delivered or custom Prompt Set (via Create Prompt Sets and the View Prompt Set report) to group interdependent prompt fields across subreports that use different data sources.
  2. Wire the Prompts tab and Data Columns: On the Prompts tab of the composite report definition, inspect all prompts for every subreport, report-level prompt, and data prompt across columns, rows, and cells. Then, inside each Data Column (under Map Sub Report Prompts), explicitly map the composite report's prompt or prompt set field to the corresponding subreport prompt.
  3. Dynamic Control Fields for Accounting Worktags: Instead of cloning a financial composite report for every worktag combination, open the Advanced tab of the composite report settings and enable Dynamic Control Fields for accounting worktags so a single report can pivot across worktag combinations at runtime.

4. Outline structures, Repeating Column Groups (RCGs), and sign reversals

Financial income statements and balance sheets rely on Outline Structures (such as Ledger Account Outline) and Repeating Column Groups (RCGs) (such as repeating Plan and Actuals columns across every Company or Fiscal Quarter):

  • Outline Effective Date default: On the Control Field Column's Outline Data section, if you leave Outline Effective Date blank, Workday defaults to Today. If a reorganization moved cost centers or ledger accounts effective next month or in a prior closed period, set the Outline Effective Date explicitly so historical or future comparisons roll up under the right hierarchy node.
  • Column outlining vs. conditional cell values: Workday disables column outlining when a cell already contains a preexisting conditional value. If you configure column outlining first, Workday restricts conditional values to calculation cells only.
  • Repeating Column Group dimension rules: Whether you set Repeating Field Value Option to Specify Value or Prompt User for Value at Run Time, every repeating field option you select must be a valid dimension in all subreports referenced by the data columns inside that RCG. Note that Workday supports RCGs on all column types except Control Field Columns, and you cannot use the Duplicate column button on columns that include an RCG.
  • Calculation columns and drill-down limits: Calculation columns support Difference, Divide, Multiply, PercentIncrease, PercentRemaining, Sum, and SumRange, plus Reverse the Sign (by column or by row category for credit-balance revenue/liability rows). If you configure a Drill Down Layout Override via Create Composite Calculation Drill Down Definition, remember that Workday does not support drilling down on custom fields.

Diagnosing composite reports in kiweely

Untangling a composite report by hand means opening the parent report and four subreports in separate tabs to compare business objects, prompt sets, and Map Fields For Join rows. When you connect your tenant in kiweely, the agent reads the composite report definition alongside every referenced subreport, runs Validate Composite Reports, identifies the exact subreport join or prompt mapping causing blank or misaligned totals, and applies the fix only after you approve it.

Sources checked