Skip to content
KiweelyKiweelyKiweely

Why a RaaS Endpoint Returns HTTP 200 with data as null in PMD and How to Surface SOAP Fault Messages

Workday RaaS JSON endpoints wrap rows inside Report_Entry instead of data, causing raasEndpoint.data to evaluate to null in PMD. Learn how to parse Report_Entry, avoid list:excludeMultiple() errors on string lists, and surface SOAP fault messages from synchronous orchestrations.

  • Checked against Workday on
  • Applies to Workday Extend
  • 3 min read
  • Published
  • By Kiweely
On this page

Why raasEndpoint.data Evaluates to null When the RaaS Call Returns HTTP 200

When you call a standard Workday REST API, WQL query (/wql/v1/data), or Extend Model Business Object collection endpoint in Presentation Metadata (PMD), Workday wraps the returned array inside a root data property (endpointName.data).

By contrast, when you expose a Workday Custom Report as a web service (RaaS) and append format=json to the endpoint URL, Workday serializes the report rows under the root key Report_Entry, not data:

json
{
  "Report_Entry": [
    {
      "Report_Definition": "INT077_Payroll_Outbound",
      "Last_Run_Date": "2026-09-08T11:30:00.000-07:00"
    },
    {
      "Report_Definition": "INT100_Benefits_Sync",
      "Last_Run_Date": "2026-09-09T08:15:00.000-07:00"
    }
  ]
}

Because raasEndpoint has no .data key, referencing raasEndpoint.data in a dropdown’s values binding or inside an onLoad script returns null even though View Application Logs shows Status Code: 200.

Reading Report_Entry and Filtering Plain String Arrays vs. Object Arrays

To populate a dropdown or pageVariables list from a RaaS JSON endpoint, reference raasEndpoint.Report_Entry ?? []. When comparing the RaaS results against an Extend Business Object endpoint (for example, excluding integration names that have already been registered in an Extend Business Object), verify whether the mapped arrays contain objects or plain strings before calling list:excludeMultiple().

In PMD scripting, list:excludeMultiple(mainList, 'keyName', comparisonList) requires mainList to be a list of JSON objects containing the property 'keyName'. If you already extracted a plain string property via .map(x => { x.Report_Definition }), each element is a string ("INT077_Payroll_Outbound"), not an object with a .descriptor key. Accessing x.descriptor throws Property Error found: descriptor.

Instead, filter plain string lists directly using .filter(x => !comparisonlist.contains(x)).distinct():

javascript
"endPoints": [
  {
    "name": "raasEndpoint",
    "baseUrlType": "WORKDAY-RAAS",
    "url": "<% 'reportOwner/TEST_All_Raas?format=json' %>",
    "httpMethod": "GET",
    "authType": "sso"
  },
  {
    "name": "getIntegrations",
    "baseUrlType": "app",
    "url": "integrations",
    "httpMethod": "GET",
    "authType": "sso",
    "isCollection": true
  }
],
"onLoad": "<%
  var reportData = raasEndpoint.Report_Entry ?? [];
  var mainlist = reportData
    .filter(x => !empty x.Report_Definition)
    .map(x => { x.Report_Definition });

  var existingintsys = getIntegrations.data ?? [];
  var comparisonlist = existingintsys
    .filter(x => !empty x.integrationSystem)
    .map(x => { x.integrationSystem });

  pageVariables.finaldropdownList = mainlist
    .filter(x => !comparisonlist.contains(x))
    .distinct()
    .map(name => {
      {
        'id': name,
        'descriptor': name
      }
    });
%>"

Converting the final filtered strings into {'id': name, 'descriptor': name} objects allows a PMD dropdown or instanceList to bind values: "<% pageVariables.finaldropdownList %>" using its default id and descriptor keys.

Surfacing SOAP Fault <wd:Message> Errors in PMD When statusCode Returns 200

A second HTTP 200 trap occurs when a PMD page invokes a Synchronous Orchestration that calls a Workday Web Services (SOAP) operation such as Organization_Add_Update or Submit_Customer_Request. When a Workday SOAP validation error occurs, the orchestration’s response wrapper returned to the PMD page often reports statusCode: 200 with the raw XML <SOAP-ENV:Fault> envelope inside the payload string:

xml
<?xml version="1.0" encoding="utf-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
  <SOAP-ENV:Body>
    <SOAP-ENV:Fault xmlns:wd="urn:com.workday/bsvc">
      <faultcode>SOAP-ENV:Client.validationError</faultcode>
      <faultstring>Validation error occurred. Invalid Subelement Custom_Organization_Reference_ID-urn:com.workday/bsvc for element Organization_Data (6$1909)</faultstring>
      <detail>
        <wd:Validation_Fault>
          <wd:Validation_Error>
            <wd:Message>Invalid Subelement Custom_Organization_Reference_ID-urn:com.workday/bsvc for element Organization_Data (6$1909)</wd:Message>
            <wd:Xpath>/bsvc:Organization_Add_Update[1]/bsvc:Organization_Data[1]/bsvc:Custom_Organization_Reference_ID[1]</wd:Xpath>
          </wd:Validation_Error>
        </wd:Validation_Fault>
      </detail>
    </SOAP-ENV:Fault>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Because PMD scripting is strictly JSON-based and has no XML/XPath parser, you cannot parse <SOAP-ENV:Fault> or <wd:Message> directly inside a PMD script.

Extracting <wd:Message> via XPath in the Synchronous Orchestration

Instead of returning raw SOAP XML to the PMD page, extract the fault status and <wd:Message> text inside the Synchronous Orchestration using Orchestration Builder’s XML member functions, and return a structured JSON response to the PMD endpoint:

  1. In your Synchronous Orchestration, inspect the output of the Send Workday API Request step (for example, SubmitCustomerRequest).
  2. In a Create Values or Create Text Template step that builds the Synchronous Orchestration’s JSON response, check whether the SOAP response is a fault (data.SubmitCustomerRequest.response.isSoapFault()) and extract the human-readable validation message using stringAtXpathWithDefault (or stringAtXPathOrEmptyString):
javascript
data.SubmitCustomerRequest.response.asXML().stringAtXPathOrEmptyString("//wd:Message")

If you also want to capture generic SOAP fault strings when <wd:Message> is absent, fall back to "//faultstring":

json
{
  "isFault": {{data.SubmitCustomerRequest.response.isSoapFault()}},
  "errorMessage": "{{data.SubmitCustomerRequest.response.asXML().stringAtXPathOrEmptyString("//wd:Message")}}",
  "xpath": "{{data.SubmitCustomerRequest.response.asXML().stringAtXPathOrEmptyString("//wd:Xpath")}}"
}
  1. On the PMD page, check syncOrchEndpoint.isFault after invoking the endpoint and pass syncOrchEndpoint.errorMessage directly to targetWidget.setError(syncOrchEndpoint.errorMessage) so the user sees the exact Workday validation message in the PMD error banner.

How to Verify in the Tenant

  1. Add console.debug(json:asJSON(raasEndpoint)); inside onLoad, open the PMD page in your tenant, and check View Application Logs to confirm the exact column XML aliases nested under Report_Entry.
  2. Verify that the dropdown populates with the deduplicated items from raasEndpoint.Report_Entry without throwing Property Error found: descriptor.
  3. Trigger a validation error against the Synchronous Orchestration from the PMD page and confirm that the XPath expression //wd:Message extracts the Workday validation message and surfaces it in the PMD page error window.

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.