Skip to content
KiweelyKiweelyKiweely

How to Map Control Fields and Related Business Objects in Workday Composite Subreports

A Workday Composite Report aligns every subreport through its Control Field column and the business objects enabled for filtering and grouping. When those objects or join mappings disagree, columns go blank or Validate Composite Reports flags Map Fields For Join exceptions.

  • Checked against Workday on
  • Applies to Workday Reporting
  • 5 min read
  • Published
  • By Kiweely
On this page

A Workday Composite Report lines up every matrix, trending, or advanced subreport against the business object on its Control Field column. When you swap a subreport or change the related business object behind a grouping dimension, you must re-enable filtering objects and remap Map Fields For Join. If those stay on the old object, Data columns go blank, Lookup columns point at the wrong attribute, and Validate Composite Reports raises join exceptions.

What the Control Field Column Actually Controls

Workday’s composite column reference describes the Control Field as the setup for:

  • The common business object used across subreport data sources
  • Combine-data-row calculations tied to control-field rows
  • The control field used by lookup data rows and lookup field value columns

You configure Control Field columns on the composite report Columns tab (or via Define on the Table tab). Every composite report needs at least one Control Field column and at least one Data column, dynamic data row, or lookup data row.

Column Type Role Relative to Control Field Constraint to Remember
Column TypeControl Field Role Relative to Control FieldShared dimension / business object anchor Constraint to RememberMultiple Control Fields disable outline display; not allowed in Repeating Column Groups
Column TypeData Role Relative to Control FieldAggregated measure from a subreport Constraint to RememberJoin-field options follow the Control Field business object
Column TypeLookup Field Value Role Relative to Control FieldAttribute of the Control Field’s business object Constraint to RememberReturn Field must be an attribute of that object; no built-in prompt fields
Column TypeCalculation Role Relative to Control FieldMath across other columns Constraint to RememberIndependent of subreport joins once source columns resolve
Column TypeEmpty Role Relative to Control FieldSpacing only Constraint to RememberNo data unless a cell override supplies it

Security for authoring sits on Custom Report Creation and Manage: All Custom Reports in the System functional area.

Enable Business Objects Before You Map Columns

Before Control Field and Data columns can see the dimensions you expect, complete Business Object Enabled for Filtering and Grouping on the composite definition:

  1. Open Edit Custom Report on the composite report.
  2. In the Business Object Enabled for Filtering and Grouping grid, select the business object that matches the dimensions used in all subreports.
  3. Optionally set Hierarchy Structure and Hierarchy Effective Date when filter criteria or lookup data rows need a hierarchy (and when you want Bulk Add Rows on the Rows tab).

Workday’s rule is strict: each subreport must reference all enabled business objects as primary or related business objects. That selection drives available values for the Control Field column, Data column, and Lookup data row. If you enable Ledger Account but one matrix subreport only groups by Cost Center, the composite cannot coherently filter or join on Ledger Account for that column.

Fails
# Enabled object and subreport dimensions disagree
Enabled for Filtering/Grouping: Ledger Account
Subreport A group-by:           Ledger Account
Subreport B group-by:           Cost Center only
Control Field:                  Ledger Account
# Subreport B cannot satisfy the enabled Ledger Account dimension
Works
Enabled for Filtering/Grouping: Ledger Account
Subreport A group-by:           Ledger Account
Subreport B group-by:           Ledger Account (same related business object)
Control Field:                  Ledger Account
Map Fields For Join:            only if alternate Ledger Account fields must coexist

Workday allows multiple business objects as dimensions on one composite report when they share the underlying related object. The documented example: Ledger Account and Ledger Account by Name both use the Ledger Account related business object and can appear together after you complete Map Fields For Join on the Data column.

Use that grid when you swap a subreport whose group-by field label changed but still points at the same related business object. Available Join Field options correspond to the business object used on the Control Field column. After edits, run Validate Composite Reports (related actions Custom Report > Validate). Workday can flag join-grid exceptions and, for some issues, offer Fix (for example removing a duplicate Web Service ID reference or repairing join exceptions). Export or screenshot the definition before using Fix.

Symptom After a Subreport Swap Likely Mismatch What to Check
Symptom After a Subreport SwapData column all zeros/blank Likely MismatchSubreport summarization field or join no longer matches Control Field What to CheckField to Aggregate, Map Fields For Join, enabled business objects
Symptom After a Subreport SwapLookup Field Value column empty Likely MismatchReturn Field not an attribute of the Control Field object What to CheckLookup Columns: Control Field Column + Return Field
Symptom After a Subreport SwapOutline missing Likely MismatchMore than one Control Field column What to CheckReduce to one Control Field if outlining is required
Symptom After a Subreport SwapValidate warnings on joins Likely MismatchStale Map Fields For Join after dimension rename What to CheckValidate Composite Reports, then remap joins

Prompt mapping is a separate layer: when the composite uses a Prompt Set and the subreport has prompts, configure Map Sub Report Prompts on the Data column so runtime criteria still flow after the swap.

Safe Sequence for Swapping a Subreport Business Object

  1. Build or edit the replacement advanced, matrix, or trending subreport so its primary or related objects include every business object enabled on the composite.
  2. On the composite, update Business Object Enabled for Filtering and Grouping if the shared dimension changed.
  3. Point the Data column at the new Sub Report Name, remap prompts, remap Map Fields For Join, and confirm Field to Aggregate still matches the subreport’s summarization type.
  4. Update Lookup Field Value columns so Return Field attributes still belong to the Control Field object.
  5. Run Validate Composite Reports, then test. Workday shows the first 10 results while testing; filters apply to all primary instances before that preview slice.

For cell-count and designer limits that appear after large rebuilds, see report cell limit exceeded and the broader composite report errors guide. Performance still depends on each subreport’s calculated fields and data sources; tune those individually with custom report performance guidance.

If you need an inherited composite’s Control Field, enabled objects, and Map Fields For Join grid traced against live subreport definitions after a dimension swap, Kiweely Vine can read the composite and subreports from your connected tenant and propose the remapping for approval. Vine Free is free for your Workday personal developer account and its tenant. Any other tenant needs Vine Personal at $99 a month for one person, or a Vine Team seat at $149 a month.

Frequently asked questions

How many Control Field columns does a Workday Composite Report need?

At least one. Workday requires a Control Field column to set the common business object across subreports. Reports with multiple Control Field columns cannot display results in an outline structure, and Control Fields are not supported inside Repeating Column Groups.

What must be true of every subreport when I enable a business object for filtering and grouping?

Each subreport must reference every enabled business object as a primary or related business object. Your Control Field, Data column, and Lookup data row prompts then draw from those enabled objects.

When do I use Map Fields For Join on a Data column?

Use Map Fields For Join when multiple business objects need to act as dimensions on the same composite report, such as Ledger Account and Ledger Account by Name sharing the Ledger Account related business object. Validate Composite Reports can flag and help fix join-grid exceptions.

How do I find broken control-field joins after swapping a subreport?

From the composite report related actions, run Custom Report Validate (or the Validate Composite Reports report). Workday lists anomalies, exceptions, and warnings, including Map Fields For Join problems when subreport joins no longer align.

Sources checked

Related guides

All guides

Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.

We’ll email you once to confirm. Unsubscribe in one click from any issue.