Skip to content
KiweelyKiweelyKiweely

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
  • Applies to Workday Extend
  • 3 min read
  • Published
  • By Kiweely
On this page

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
Model Component ScopeTotal SINGLE_INSTANCE + MULTI_INSTANCE fields per Business Object Platform Limit10 per business object
Model Component ScopeTotal fields (all types) per Business Object Platform Limit50 per business object
Model Component ScopeBusiness Objects per Extend App Platform Limit20 per app
Model Component ScopeSINGLE_INSTANCE and MULTI_INSTANCE fields targeting Workday-delivered Business Objects across the entire app Platform Limit25 per app
Model Component ScopeSINGLE_INSTANCE fields with enableReportingFromTarget: true Platform Limit5 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

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.