---
title: "Fix Missing GraphQL Attachment Schema in IMPL Tenants"
description: "Resolve Unknown type _DataSources and missing contentType errors on Extend Attachment Business Objects in GraphQL after promoting an app to Implementation."
url: https://kiweely.com/guides/workday-graphql-attachment-schema-contenttype-missing-impl
---

# Why Attachment Model Components and contentType Are Missing from the GraphQL Schema After Migrating to IMPL

After promoting a Workday Extend app with an Attachment Business Object to an Implementation or Sandbox tenant, GraphQL queries can fail with Unknown type \_DataSources or missing contentType fields. Refresh the model cache, verify ISU domain security, and check tenant Graph schema availability.

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

## Why GraphQL attachment queries fail after promoting from DEV to IMPL or Sandbox

When you promote a Workday Extend application containing a Model Business Object (`MBO`) or an Attachment Model Component from a Development (`WCPDEV`) tenant to an Implementation (`IMPL`) or Sandbox tenant, pages that query the attachment object through the Workday Graph API (`baseUrlType: "workday-graphql"` or `"workday-graph"`) can fail on load with two schema errors:

1.  **Missing Attachment Data Source Type:**

json

```
{
  "errors": [
    {
      "message": "Unknown type 'Trail2journalload_jbqjlf_AttachJournal_DataSources'. (line 1, column 98):\nquery trail2journalload_jbqjlf_AttachJournal($trail2journalload_jbqjlf_AttachJournal_dataSource: Trail2journalload_jbqjlf_AttachJournal_DataSources!)",
      "locations": [{ "line": 1, "column": 98 }]
    },
    {
      "message": "Cannot query field 'trail2journalload_jbqjlf_AttachJournal' on type 'Query'.",
      "locations": [{ "line": 2, "column": 3 }]
    }
  ]
}
```

1.  **Missing `contentType` Field on the Attachment RBO:** A GraphQL query that reads `contentType` from an Attachment Related Business Object (`RBO`) to populate the `fileType` attribute of a `fileUploaderRow` widget works in `WCPDEV`, but fails in `IMPL` because `contentType` does not appear on the Attachment type in the `IMPL` GraphQL schema even though `WQL` can query `contentType` on the same object.

## Step 1: Verify the Model Component promotion window and refresh the tenant cache

Extend apps that include Model Components (Business Objects, Attachment Objects, Security Domains, and Model Business Processes) follow Workday’s weekly Model Component promotion schedule (submitted before the Thursday cutoff and applied during the weekly maintenance window). If an app is promoted after the cutoff or if the target tenant was recently refreshed from Production, the GraphQL schema in the target tenant will not immediately expose the `<App>_<Object>_DataSources` type.

Once the Model Component version is active in the target tenant:

1.  Run the **Refresh Extend Model Component Cache** task in the `IMPL` or Sandbox tenant.
2.  Open the custom security domain created for your application (`<App>_Security_Domain`). If the Functional Area was not automatically attached in the target tenant, assign the domain to its Functional Area, add your Integration System Security Group (`ISSG`) or user security groups to both **View** and **Modify** permissions, and run **Activate Pending Security Policy Changes**.
3.  Ensure that the calling security group also has **View** permission on the **Graph API Descriptor** and **Workday Graph API Applications** system domains in the target tenant.

## Step 2: Check `authType: "isuAuth"` and connect Graph API Explorer directly to IMPL

Workday hides any Model Business Object or Attachment Object from the generated GraphQL schema if the authenticated caller lacks domain security permissions to read that object. When the caller has no read access, GraphQL does not return a `403 Forbidden` status; instead, it omits the object’s query field and `DataSources` enum from the caller’s view of the schema, producing `Unknown type '<App>_<Object>_DataSources'` and `Cannot query field '<app>_<object>' on type 'Query'`.

1.  In your `.pmd` file, verify whether the attachment endpoint uses `"authType": "isuAuth"` or `"authType": "sso"`.
2.  If it uses `"authType": "isuAuth"`, open **App Manager** in the `IMPL` tenant, confirm the Simplified Integration System User (`WCPISU` or custom ISU) is registered to the app via **Add Integration User**, and verify that its `ISSG` is included on the security domain securing the Attachment Model Component.
3.  Open **Graph API Explorer** on the Workday Developer Site, switch the connected tenant dropdown specifically to your **IMPL** tenant (do not leave it connected to `WCPDEV`), and inspect the **Documentation Explorer** sidebar to confirm whether `<app>_<attachmentObject>` appears under `Query`.

json

```
{
  "name": "createDocuments",
  "baseUrlType": "workday-graphql",
  "exclude": "<% empty docUpload.children %>",
  "httpMethod": "POST",
  "authType": "isuAuth",
  "graphQuery": {
    "queryId": "createEmployeeDocuments",
    "variables": {
      "PracticeApp_abcdde_createEmployeeDocumentsCollection_input": {
        "employeeDocuments": "<%
          docUpload.rows.map((row, index) => {
            return {
              'attachmentContent': 'file' + index,
              'createdAt': date:getTodaysDate(date:getDateTimeZone(userTimeZone)),
              'createdBy': graph:createId(currentLoginUser.id),
              'category': docCategory.value ?? ''
            };
          })
        %>"
      }
    }
  }
}
```

## Step 3: Handling `contentType` schema differences between WCPDEV and IMPL

When an Attachment object is queried as an RBO on a parent Model Business Object to render existing attachments inside a `fileUploader` / `fileUploaderRow` widget, developers often select `contentType` alongside `fileName`, `downloadID`, and `workdayID`:

graphql

```
query getJournalRecord($dataSource: MyApp_abcdde_Journal_DataSources!) {
  myApp_abcdde_Journal(dataSource: $dataSource) {
    data {
      workdayID {
        id
      }
      journalAttachments {
        data {
          workdayID {
            id
          }
          fileName
          downloadID
        }
      }
    }
  }
}
```

Because Graph API schema features are gated by environment confidence levels across `WCPDEV` and `IMPL` tenants, a newly introduced field like `contentType` on an Attachment RBO can be visible in `WCPDEV` while omitted from the `IMPL` Graph schema until the feature toggle rolls out to all environments.

If `Graph API Explorer` connected to `IMPL` shows `fileName` and `downloadID` on your Attachment type but does not list `contentType`:

-   Remove `contentType` from the GraphQL selection set so the Graph query succeeds in `IMPL`.
-   Derive the MIME type from the `fileName` extension in PMD script, or query the attachment metadata (`SELECT workdayID, fileName, contentType FROM <app>_<attachmentBO>`) through a `WORKDAY-WQL` endpoint where `contentType` is exposed across all tenant types.

## How to verify the fix in your tenant

1.  Connect **Graph API Explorer** on the Workday Developer Site directly to your `IMPL` or Sandbox tenant.
2.  Search the **Documentation Explorer** panel for your `<app>_<attachmentObject>` query and inspect every field listed under the Attachment type.
3.  Run the exact query from your `.pmd` `graphQueries` block in **Graph API Explorer** against `IMPL` and verify that it returns `"data"` with zero schema validation errors before opening the Extend page in the tenant.

## Sources checked

-   [Model Components in the Graph API Schema](https://developer.workday.com/documentation/xng1652977416314)
-   [Graph API Attachments](https://developer.workday.com/documentation/GUID-f55baa31-61f8-441e-bd0a-2482ad551254-enHYPHENus)
-   [Workday Graph API Authentication and Security](https://developer.workday.com/documentation/GUID-8b37afd9-22d7-42ba-b150-e979466f1525-enHYPHENus)
-   [Graph API in Extend Pages](https://developer.workday.com/documentation/xfa1653188971557)
-   [Reference: Promotion Deadlines for Extend Apps with Model Components](https://developer.workday.com/documentation/giw1660842903762)

## Related guides

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

-   [### Handling Silent GraphQL Errors in PMD and Orchestrate When HTTP Status Returns 200 OK Workday Graph API endpoints return HTTP 200 OK even when a query or mutation fails with an S21 or validation error inside the JSON errors array. Inspect $.errors explicitly in Orchestrate and verify that your .amd base URL version matches Graph API Explorer.](https://kiweely.com/guides/workday-graphql-http-200-silent-mutation-errors)
-   [### Fixing Graph API DataSourceFilter Is Inaccessible Errors and Blank processingWorker Fields When Proxying Workday Graph API queries fail with DataSourceFilter is inaccessible when the caller lacks View access to the domain securing the filter, and silently return blank fields on processingWorker when Employee As Self lacks contact domain permissions.](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 Workday Graph API mutations require nested IdentifierInput objects for single-instance relationships like createdBy—which you can generate cleanly in PMD with graph:createId(id). To clear an existing single-instance relationship back to null, use the Model Business Object REST PUT or PATCH API.](https://kiweely.com/guides/workday-graphql-clear-single-instance-null-graph-createid)
-   [### Why fileLength on workerDocuments Returns 52 in WQL for Business Process Attachments Querying fileLength on the workerDocuments related business object in WQL returns a constant 52 (or 0) whenever the document was attached through a business process event. Retrieve the actual byte length in Workday Orchestrate using Data.contentLength().](https://kiweely.com/guides/wql-workerdocuments-filelength-returns-52)

### More guides on Extend apps and pages

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

-   [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)
-   [Deleting Selected Grid Rows and Fixing Parallel Multi-Instance Arrays Collapsing on Edit Pages in Workday Extend PMD](https://kiweely.com/guides/workday-extend-pmd-grid-delete-selected-rows-parallel-arrays-collapse)
-   [Displaying dynamicColumns in a Workday Extend PMD Grid and Flattening Nested Arrays into Rows](https://kiweely.com/guides/workday-extend-pmd-dynamic-grid-columns-flattening-arrays)
-   [Conditional Page Routing on Load, multiStepLayout vs. tabBar Navigation, and flowVariables Payload Limits in Workday Extend PMD](https://kiweely.com/guides/workday-extend-pmd-conditional-page-routing-tabbar-flowvariables-limits)
-   [Clearing Grid Cell Validation Errors on onChange and Blocking Page Save on pageActionButton Failure in Workday Extend PMD](https://kiweely.com/guides/workday-extend-pmd-clear-grid-cell-error-pageactionbutton-block-save)

### From the blog on Extend apps and pages

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

-   [Workday Extend vs. Power Apps and ServiceNow App Engine: where to build a Workday app](https://kiweely.com/blog/workday-extend-vs-power-apps-servicenow-app-engine)
-   [What can you change in a Workday Extend app after its model components deploy?](https://kiweely.com/blog/workday-extend-model-components-first-deploy)
-   [How do you test a Workday Extend app end to end?](https://kiweely.com/blog/test-workday-extend-app-end-to-end)

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