---
title: "Map Control Fields in Workday Composite Reports — Kiweely"
description: "Align Workday Composite Report Control Field columns with subreport business objects, enable filtering objects, and fix Map Fields For Join when dimensions…"
url: https://kiweely.com/guides/workday-composite-report-control-fields-business-object-swap
---

# 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 November 13
-   Applies to **Workday Reporting**
-   5 min read
-   Published November 13
-   By Kiweely

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 |
| --- | --- | --- |
|  **Control Field** | Shared dimension / business object anchor | Multiple Control Fields disable outline display; not allowed in Repeating Column Groups |
|  **Data** | Aggregated measure from a subreport | Join-field options follow the Control Field business object |
|  **Lookup Field Value** | Attribute of the Control Field’s business object | Return Field must be an attribute of that object; no built-in prompt fields |
|  **Calculation** | Math across other columns | Independent of subreport joins once source columns resolve |
|  **Empty** | Spacing only | No 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
```

## Map Fields For Join When Related Objects Differ by Label

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 |
| --- | --- | --- |
| Data column all zeros/blank | Subreport summarization field or join no longer matches Control Field | Field to Aggregate, Map Fields For Join, enabled business objects |
| Lookup Field Value column empty | Return Field not an attribute of the Control Field object | Lookup Columns: Control Field Column + Return Field |
| Outline missing | More than one Control Field column | Reduce to one Control Field if outlining is required |
| Validate warnings on joins | Stale Map Fields For Join after dimension rename | Validate 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](https://kiweely.com/guides/workday-report-cell-limit-exceeded-exception) and the broader [composite report errors](https://kiweely.com/guides/workday-composite-report-errors) guide. Performance still depends on each subreport’s calculated fields and data sources; tune those individually with [custom report performance guidance](https://kiweely.com/guides/workday-slow-custom-report-performance-tuning).

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](https://kiweely.com/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

-   [Concept: Composite Reports](https://doc.workday.com/admin-guide/en-us/reporting-and-analytics/custom-reports-and-analytics/composite-reports/nea1439395613969.html)
-   [Enable Business Objects for Filtering and Grouping](https://doc.workday.com/admin-guide/en-us/reporting-and-analytics/custom-reports-and-analytics/composite-reports/nea1447354512795.html)
-   [Set Up Composite Report Columns](https://doc.workday.com/admin-guide/en-us/reporting-and-analytics/custom-reports-and-analytics/composite-reports/nea1439402225879.html)
-   [Reference: Composite Report Columns](https://doc.workday.com/admin-guide/en-us/reporting-and-analytics/custom-reports-and-analytics/composite-reports/nea1443135464830.html)
-   [Steps: Create Composite Reports](https://doc.workday.com/admin-guide/en-us/reporting-and-analytics/custom-reports-and-analytics/composite-reports/dan1405963000012.html)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### How to Fix CellLimitExceededException: Exceeded Cell Limit in Workday Custom Reports and EIBs CellLimitExceededException and exceeded cell limit errors happen when a Workday custom report, outbound EIB, or workbook crosses grid-cell, multi-instance expansion, or 32,767-character cell limits. Switch large extracts to CSV, flatten multi-instance columns, and tighten indexed filters.](https://kiweely.com/guides/workday-report-cell-limit-exceeded-exception)
-   [### How do I group, aggregate and drill down in Workday advanced, matrix and composite reports? Advanced reports group with Sort and Group and aggregate per column, matrix reports use row and column groupings, and composite reports combine subreports and drill through links on the composite itself. Worked examples below.](https://kiweely.com/guides/workday-matrix-reports-aggregations-drilldowns)
-   [### Slow Workday Custom Reports: Fixing Data Source Filter and Calculated Field Timeouts Diagnose and resolve slow Workday custom reports and RaaS timeouts. Replace broad data sources with indexed RDSs and built-in data source filters, check Optimized for Performance, prune deep calculated field chains, and run Custom Report Exception Audit.](https://kiweely.com/guides/workday-slow-custom-report-performance-tuning)
-   [### Workday Calculated Fields: How to Build Them and Fix Common Errors Choose the business object and scope, configure three core functions, and fix missing fields, empty results and incorrect conditions. Examples use Workday’s documented fields and options.](https://kiweely.com/guides/workday-calculated-fields)
-   [### Workday composite reports: fix Map Fields For Join errors, prompt sets and subreport problems A composite report combines matrix, trending or advanced subreports on a shared control field and outline structure. When it breaks, check subreport eligibility, Map Fields For Join, prompt mapping and Repeating Column Groups, then run Validate Composite Reports.](https://kiweely.com/guides/workday-composite-report-errors)

### More guides on Extend apps and pages

[All 97 guides](https://kiweely.com/guides#extend)

-   [Workday Lookup Related Value (LRV) Explained: Crossing Business Objects Without Blank Rows](https://kiweely.com/guides/workday-lookup-related-value-lrv-calculated-field)
-   [Fixing Graph API DataSourceFilter Is Inaccessible Errors and Blank processingWorker Fields When Proxying](https://kiweely.com/guides/workday-graphql-datasourcefilter-inaccessible-processingworker-proxy)
-   [Clearing Single-Instance Relationships to Null and Binding createdBy with graph:createId() in Graph API](https://kiweely.com/guides/workday-graphql-clear-single-instance-null-graph-createid)
-   [Why Attachment Model Components and contentType Are Missing from the GraphQL Schema After Migrating to IMPL](https://kiweely.com/guides/workday-graphql-attachment-schema-contenttype-missing-impl)
-   [Splitting New and Existing PMD Grid Rows in onSend for Bulk POST and PATCH Without Duplicating Records](https://kiweely.com/guides/workday-extend-pmd-split-new-modified-grid-rows-bulk-post-patch)
-   [Fixing radioGroup Options Disappearing When selectedValues Is Empty and Disabling Specific Options in Workday Extend PMD](https://kiweely.com/guides/workday-extend-pmd-radiogroup-options-disappear-disable-specific-items)
-   [Why a RaaS Endpoint Returns HTTP 200 with data as null in PMD and How to Surface SOAP Fault Messages](https://kiweely.com/guides/workday-extend-pmd-raas-report-entry-null-soap-fault-http-200)
-   [Why PATCH from an SSO PMD Page Fails with unrecognized field While the Same Payload Succeeds in Postman](https://kiweely.com/guides/workday-extend-pmd-patch-unrecognised-field-sso-vs-postman)

### From the blog on Extend apps and pages

[All posts](https://kiweely.com/blog)

-   [Workday Opened Extend to Individual Developers. Here’s What It Changes](https://kiweely.com/blog/workday-opens-extend-to-individual-developers)
-   [Debugging Workday Extend web services: Postman vs. kiweely](https://kiweely.com/blog/debugging-workday-extend-web-services-postman-vs-kiweely)
-   [Rapid ideation and prototyping of Workday Extend apps](https://kiweely.com/blog/rapid-prototyping-workday-extend-apps-with-kiweely)

## Let Workday check the work.

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

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

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