---
title: "Workday Extend MCBO 10-Relationship Limit & Helper BO"
description: "Overcome the 10 SINGLE_INSTANCE and MULTI_INSTANCE relationship limit per Workday Extend Model Business Object using a 1:1 helper extension object."
url: https://kiweely.com/guides/workday-extend-mcbo-10-single-instance-relationship-limit-helper-bo
---

# Working Around the 10-Relationship Limit on a Workday Extend Model Business Object (MCBO) Using a Helper Object

Workday Extend enforces a platform ceiling of 10 SINGLE\_INSTANCE and MULTI\_INSTANCE relationship fields per Model Business Object (MCBO) and 25 delivered target relationships per app. Learn how to reserve the 10th slot for a 1:1 helper extension object and query across both objects in WQL.

-   **Checked** against Workday on November 6
-   Applies to **Workday Extend**
-   3 min read
-   Published November 6
-   By Kiweely

## Understanding Workday Extend’s 10-Relationship Limit per Model Business Object

Workday Extend enforces strict schema limits on Model Components. While each Model Business Object (MCBO) can define up to 50 total fields and 40 derived fields, the platform caps **`SINGLE_INSTANCE` and `MULTI_INSTANCE` relationship fields at 10 per business object**:

| Model Component Scope | Platform Limit |
| --- | --- |
| Total `SINGLE_INSTANCE` + `MULTI_INSTANCE` fields per Business Object |  **10 per business object** |
| Total fields (all types) per Business Object |  **50 per business object** |
| Business Objects per Extend App |  **20 per app** |
| `SINGLE_INSTANCE` and `MULTI_INSTANCE` fields targeting Workday-delivered Business Objects across the entire app |  **25 per app** |
| `SINGLE_INSTANCE` fields with `enableReportingFromTarget: true` |  **5 per app** |

When a complex primary record—such as a global job evaluation, capital request, or position requisition—already uses 9 `SINGLE_INSTANCE` fields to reference delivered Workday objects (`Worker`, `Supervisory_Organization`, `Cost_Center`, `Location`, `Company`, `Job_Profile`, `Grade`, `Currency`, `Position`) and the business requests three more relationship fields, adding them directly to the primary MCBO fails deployment validation once you exceed 10 relationship fields.

## Designing the 1:1 Helper Extension Business Object Pattern

Before consuming the 10th relationship slot on your primary Business Object with another domain reference, reserve that 10th `SINGLE_INSTANCE` slot to link to a **Helper / Extension Business Object** (`MCBO_Extension`).

### Bidirectional 1:1 Linking Between Primary and Helper Objects

1.  **Primary Business Object (`RequisitionRequest`)**:
    -   Retains its first 9 `SINGLE_INSTANCE` / `MULTI_INSTANCE` relationship fields.
    -   Uses its **10th `SINGLE_INSTANCE` field** (`extensionDetails`) to reference the custom `RequisitionRequestExtension` Business Object.
2.  **Helper Business Object (`RequisitionRequestExtension`)**:
    -   Uses its **1st `SINGLE_INSTANCE` field** (`parentRequisition`) to point back to `RequisitionRequest` so custom reports and WQL queries starting from the helper object can traverse back to the parent record.
    -   Uses its **remaining 9 relationship slots** (fields 2 through 10) to store additional `SINGLE_INSTANCE` or `MULTI_INSTANCE` references (or reserves its own 10th slot if further chaining is ever required, subject to the app-wide ceiling of 25 relationships targeting Workday-delivered Business Objects).

json

```
{
  "name": "RequisitionRequestExtension",
  "label": "Requisition Request Extension",
  "securingDomains": ["RequisitionSecurityDomain"],
  "fields": [
    {
      "id": 1,
      "name": "parentRequisition",
      "label": "Parent Requisition",
      "type": "SINGLE_INSTANCE",
      "businessObject": "RequisitionRequest"
    },
    {
      "id": 2,
      "name": "secondaryCostCenter",
      "label": "Secondary Cost Center",
      "type": "SINGLE_INSTANCE",
      "businessObject": "Workday_Cost_Center"
    },
    {
      "id": 3,
      "name": "projectWorktag",
      "label": "Project Worktag",
      "type": "SINGLE_INSTANCE",
      "businessObject": "Workday_Project"
    },
    {
      "id": 4,
      "name": "approvingDivision",
      "label": "Approving Division",
      "type": "SINGLE_INSTANCE",
      "businessObject": "Workday_Custom_Organization"
    }
  ]
}
```

Share the same `securingDomains` across both `RequisitionRequest` and `RequisitionRequestExtension` so users and Integration System Users (ISUs) have consistent read and write access to both halves of the record.

## Creating and Updating Both Objects from PMD or Orchestrate

When a user submits a Create page in PMD that captures fields belonging to both the primary and helper objects, sequence the outbound endpoints or use a Synchronous Orchestration so the helper object is created and linked cleanly:

1.  **POST the Helper Object (`createExtensionBo`)**: Create the `RequisitionRequestExtension` instance first (populating `secondaryCostCenter`, `projectWorktag`, and `approvingDivision`), which returns `createExtensionBo.id`.
2.  **POST the Primary Object (`createPrimaryBo`)**: Create the `RequisitionRequest` instance and pass `{"id": createExtensionBo.id}` into the 10th relationship field `extensionDetails`:

json

```
"outboundData": {
  "outboundEndPoints": [
    {
      "name": "createExtensionBo",
      "baseUrlType": "app",
      "url": "requisitionRequestExtensions",
      "httpMethod": "POST",
      "authType": "sso",
      "onSend": "<%
        return {
          'secondaryCostCenter': { 'id': secondaryCostCenterList.value[0] },
          'projectWorktag': { 'id': projectList.value[0] },
          'approvingDivision': { 'id': divisionList.value[0] }
        };
      %>"
    },
    {
      "name": "createPrimaryBo",
      "baseUrlType": "app",
      "url": "requisitionRequests",
      "httpMethod": "POST",
      "authType": "sso",
      "onSend": "<%
        return {
          'worker': { 'id': workerList.value[0] },
          'supervisoryOrganization': { 'id': supOrgList.value[0] },
          'extensionDetails': { 'id': createExtensionBo.id }
        };
      %>"
    },
    {
      "name": "linkParentOnExtensionBo",
      "baseUrlType": "app",
      "url": "<% 'requisitionRequestExtensions/' + createExtensionBo.id %>",
      "httpMethod": "PATCH",
      "authType": "sso",
      "onSend": "<%
        return {
          'parentRequisition': { 'id': createPrimaryBo.id }
        };
      %>"
    }
  ]
}
```

## Querying Across Primary and Helper MCBOs in WQL and RaaS

Because `extensionDetails` is a `SINGLE_INSTANCE` Related Business Object (RBO) on `RequisitionRequest`, you can fetch fields from both the primary object and the helper object in a single WQL query using RBO brace notation `{...}`:

sql

```
SELECT workdayID,
       worker,
       supervisoryOrganization,
       extensionDetails {
         workdayID,
         secondaryCostCenter,
         projectWorktag,
         approvingDivision
       }
FROM customApp_requisitionRequests
WHERE workdayID = '8a49c1209f111000142a907b2c310000'
```

Likewise, in Workday Custom Reports (RaaS), add `Extension Details` as a Related Business Object column on a report built on the `Requisition Request` data source to surface all 18 relationship fields in a single flat report output.

## How to Verify in the Tenant

1.  Deploy both Model Business Objects (`RequisitionRequest` and `RequisitionRequestExtension`) to your Workday Extend development tenant and confirm that schema validation passes with 10 relationships on the primary object.
2.  Submit the PMD creation page to create a linked pair of records and verify in **View WQL Query Result** that the nested RBO query `SELECT extensionDetails { secondaryCostCenter, projectWorktag } FROM ...` returns the related Workday objects.
3.  Verify the reverse link by querying the helper data source (`SELECT parentRequisition { worker } FROM customApp_requisitionRequestExtensions`) to confirm bidirectional reporting works.

## Sources checked

-   [Reference: Limits on Model Components](https://developer.workday.com/documentation/GUID-7d78b63a-766a-449c-839c-f7080e7e67aa)
-   [Get Started with Model Business Objects](https://developer.workday.com/documentation/GUID-e371c038-c97f-4518-a18e-eafed4670bc5-enHYPHENus)
-   [Concept: Related Business Objects in WQL](https://developer.workday.com/documentation/GUID-5295e235-6d69-4b80-ad51-510afbdfb853-enHYPHENus)
-   [Reference: Business Object API Requests](https://developer.workday.com/documentation/xml1559763881756)

## Related guides

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

-   [### Deleting Selected Grid Rows and Fixing Parallel Multi-Instance Arrays Collapsing on Edit Pages in Workday Extend PMD Workday Extend PMD does not permit outbound DELETE calls inside onRowSelect, and storing grid columns as separate multi-instance fields on a single BO record causes edit grids to collapse into one row. Learn how to handle row deletion on submit and zip parallel arrays by index.](https://kiweely.com/guides/workday-extend-pmd-grid-delete-selected-rows-parallel-arrays-collapse)
-   [### How to Blank Out Text Fields and Nullify Reference Values on Workday Extend Business Objects via Inbound EIB Using {empty} Leaving a spreadsheet cell blank or entering “” or null in an Inbound EIB does not clear existing field values on a Workday Extend Business Object. Learn how to use the {empty} tag, avoid the leading/trailing whitespace trap in Excel, and remove specific multi-instance values.](https://kiweely.com/guides/workday-extend-eib-clear-text-nullify-fields-empty-tag)
-   [### Fixing “Object instance has properties which are not allowed by the schema (parentBusinessProcesses, initiationPageRoute)” on Extend Subprocesses Adding an Extend Model Business Process as a subprocess of a delivered Workday business process fails validation if parentBusinessProcesses and initiationPageRoute are placed at the root of the .bp file or omit the {eventStepId} parameter. Learn the complete .bp, .amd, and .pmd configuration.](https://kiweely.com/guides/workday-extend-bp-subprocess-allowedparentprocesses-eventstepid)

### More guides on Extend apps and pages

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

-   [Cascading dropdowns and instance lists in Workday Extend](https://kiweely.com/guides/workday-extend-cascading-instance-lists)
-   [How to move Workday Extend apps to a new developer tenant before the old one expires or is deleted](https://kiweely.com/guides/workday-extend-move-apps-new-developer-tenant)
-   [Why a Workday Graph API query suddenly fails with “Cannot query field”](https://kiweely.com/guides/workday-graphql-cannot-query-field)
-   [How to build a worker search prompt in a Workday Extend page](https://kiweely.com/guides/workday-extend-worker-search)
-   [Which Workday Extend widget to use for what](https://kiweely.com/guides/workday-extend-widget-guide)
-   [Workday Extend Professional is now Extend AI: Core vs AI vs legacy limits, storage and AI features](https://kiweely.com/guides/workday-extend-legacy-vs-extend-professional)
-   [Model business processes in Workday Extend: how a transaction gets created and approved](https://kiweely.com/guides/workday-extend-model-business-process)
-   [Version control for Workday Extend apps: GitHub, Local Disk Sync and automated deploys](https://kiweely.com/guides/workday-extend-version-control-github)

### From the blog on Extend apps and pages

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

-   [What functional consultants can and cannot do with Workday Extend AI](https://kiweely.com/blog/workday-extend-for-functional-consultants-ai)
-   [Put a Workday Extend App in Git from Day One](https://kiweely.com/blog/workday-extend-git-from-day-one)
-   [Pairing Claude Code with a Personal Workday Extend Tenant for Portfolio Apps](https://kiweely.com/blog/claude-code-personal-workday-extend-tenant-portfolio)

## 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.
