---
title: "Workday Extend PMD page errors: what's actually failing"
description: "Why a Workday Extend page returns nothing, hits a 403, breaks on a binding or script, or doesn't appear in the tenant, and where the fix really belongs."
url: https://kiweely.com/guides/workday-extend-pages-errors
---

# Workday Extend PMD page errors: what’s actually failing

A PMD error is a break in one of three places: the endpoint call, a binding to a value that isn’t there, or a script that touches a field before checking it.

-   **Checked** against Workday on September 22
-   Applies to **Workday Extend**
-   4 min read
-   Published September 22
-   By Kiweely

## What a Workday Extend page actually is

A Workday Extend page is defined by a PMD (Presentation Model Definition) component. Workday’s own Extend App Components Reference groups PMDs, along with app preview, under a “Pages” section, so “page” and “PMD” describe the same file. The PMD lists widgets, the endpoints those widgets read or write, and the bindings that connect a widget to a field in an endpoint’s response.

An endpoint’s host comes from a separate file: the AMD (App Metadata Document) declares a `dataProviders` entry whose `key` the PMD’s endpoint references as `baseUrlType`. A page error is almost always a break in one of three places: the endpoint call itself, a binding that expects a value the endpoint never returned, or a script that touches a field before checking it exists. Read the message, then find which of the three it actually names before changing anything.

## The endpoint returns nothing, or a 403

An inbound or outbound endpoint calling a Workday REST API needs four things on the PMD side — `name`, `baseUrlType`, `url`, and `authType` — plus a matching `dataProviders` entry on the AMD supplying the real host for that `baseUrlType`:

```
{ "key": "workday-common", "value": "<% apiGatewayEndpoint + '/common/v1/' %>" }
```

A blank widget with no visible error usually means the call never reached Workday, or reached it and was rejected silently. Workday secures every REST method with a security domain or business process security policy, and a signed-in user or the app’s own system user needs the matching Report/Task permission. A 403 from that check does not automatically become a page error: by default, Presentation Components only route 301, 302, 303, 307, 401, 404, 407, 408, 500 and 503 to a custom error page. 403 is not on that list, so a security rejection can render as an empty widget instead of a message. To make it visible, opt that endpoint’s own 403 into `failOnStatusCodes`:

```
{
  "name": "worker",
  "baseUrlType": "workday-common",
  "url": "workers/me",
  "authType": "sso",
  "failOnStatusCodes": [{ "code": 403 }]
}
```

Mapping the code under the site’s `errorPageConfigurations` alone does nothing; the endpoint has to name the code before Workday will route it anywhere.

## Bindings to a value that isn’t there

A widget’s `value` or `valueOutBinding` points at a JSON path in an endpoint’s response:

```
"value": "<% worker.data.descriptor %>"
```

This fails quietly when the field is optional and the current record simply doesn’t have it — a worker with no manager, a request with no attachment — rather than when the endpoint itself is broken. Confirm what the endpoint actually returned for that record before assuming the binding path is wrong; a field that exists for one test record and not another is a data condition to design for, not a syntax bug to chase.

## Script errors: reading a field that isn’t there

PMD Scripting reads like JavaScript but is its own language, so test for absence the way Workday’s examples do: call `.isEmpty()` on the value, and negate it with `!` when you want the present case. A field that is missing on some records needs the check before the read, not after:

```
<%
  if (!worker.data.manager.isEmpty())
    worker.data.manager.descriptor
  else
    'Unassigned'
%>
```

When a script error names a line, reproduce it with the record that failed. A script that works for one test worker and fails for another is almost always reading an optional field without this check.

## The page doesn’t show up in the tenant

When a page that validates and builds still isn’t reachable for a user, the cause is usually outside the PMD. Check, in order: the app was actually deployed to the tenant being tested (a successful build is not the same event as a deploy); the task or route that opens the page is assigned to the user’s security group; and any security domain or business process policy the page’s own endpoints depend on is active, not left as a pending policy change. A page that opens for one role and not another is almost always a security-group gap, not a PMD defect — compare the working and failing role’s group membership before touching the page source.

## Preview behaves differently than the deployed page

App Preview is fast for checking layout and page logic, and it can run against mock endpoint responses without touching a tenant. Workday documents that preview does not behave identically to a deployed app in every respect — including security and timezone handling — so a page that looks right in preview can still fail once deployed, and the reverse also happens. Treat a preview pass as evidence about layout and script logic only; confirm security-dependent and timezone-dependent behavior against a deployed Development, Implementation or Sandbox app.

## Prove the fix at the layer that failed

Reproduce the exact finding, change the smallest thing that removes it, and recheck the same layer — an endpoint fix needs a live call to prove it, a security fix needs the actual role to reopen the page, watched in a real browser rather than trusted from a green build alone. For component-level rejections, use [the validation-error guide](https://kiweely.com/guides/workday-extend-validation-errors); for full journey proof, use [the testing guide](https://kiweely.com/guides/workday-extend-testing). Flow and orchestration failures reached from a page belong in [the Orchestrate errors guide](https://kiweely.com/guides/orchestrate-errors). kiweely carries an Extend app through this loop end to end; see [/extend](https://kiweely.com/extend).

## Sources checked

-   [Workday Extend](https://developer.workday.com/documentation/yti1557429833671)
-   [Call Workday REST APIs in Extend apps](https://developer.workday.com/documentation/gya1560920237072)
-   [Custom error pages](https://developer.workday.com/documentation/vfx1525988737823)
-   [Extend App Preview](https://developer.workday.com/documentation/xww1669752564537)
-   [Workday Extend app lifecycle](https://developer.workday.com/documentation/cjw1620248412279)
-   [Application Logs](https://developer.workday.com/documentation/hlt1558652308211)

## Related guides

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

-   [### How should I test a Workday Extend app before promoting it to production? Test in the order Workday promotes: App Preview and mock data, a Development tenant, Implementation for QA, then Sandbox with production data for acceptance. Promote to Production only after each stage has recorded evidence, because installed apps cannot be removed.](https://kiweely.com/guides/workday-extend-testing)
-   [### How do I find the real cause of a Workday Extend app validation error? First work out which check rejected the app: the App Builder Validate pane, the build log from Save to App Hub, the deploy, or the running page. Then match the code (E102, P300, B100) to Workday’s own text, fix that one cause and rerun the same check.](https://kiweely.com/guides/workday-extend-validation-errors)
-   [### How do I debug a Workday Orchestrate orchestration that shows success but some steps failed? A run can look successful because an unsuccessful HTTP response is not a failure unless a retry policy defines a success range, and an error handler set to Conditional Outputs lets the run carry on. Read the run’s per-process stepsFailed, not the status.](https://kiweely.com/guides/orchestrate-errors)

### More guides on Extend apps and pages

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

-   [Workday UI Automation Testing: Why Scripts Break and How to Automate Reliably](https://kiweely.com/guides/workday-ui-automation-testing)
-   [Why does a PMD endpoint fail when the key is lowercase endpoints?](https://kiweely.com/guides/workday-pmd-endpoint-lowercase-keys)
-   [What does Extend PMD “failed to resolve a definition” mean?](https://kiweely.com/guides/workday-extend-pmd-failed-to-resolve-definition)
-   [Why does an Extend edit page show Internal Server Error on submit?](https://kiweely.com/guides/workday-extend-internal-server-error-on-submit)
-   [How do I fix “Failed to generate WUL from PMD snippet” in Extend?](https://kiweely.com/guides/workday-extend-failed-to-generate-wul-from-pmd)
-   [Why does my Extend custom validation message never display?](https://kiweely.com/guides/workday-extend-custom-validation-error-not-displayed)
-   [How do I migrate a Workday Extend app from WCPISU to simplified ISU?](https://kiweely.com/guides/workday-migrate-wcpisu-to-simplified-isu)
-   [What is known about a December 2026 Extend model components compiler upgrade?](https://kiweely.com/guides/workday-extend-model-compiler-upgrade-2026-12)

### From the blog on Extend apps and pages

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

-   [Five Workday Extend app blueprints you can build in a free personal tenant](https://kiweely.com/blog/five-workday-extend-apps-to-build-in-open-developer-program)
-   [From Business Brief to Tested Workday Extend App: Why Zero Validation Errors Is Not Proof](https://kiweely.com/blog/why-workday-extend-validation-is-not-testing)
-   [Workday Extend Graph API and AppHub Promotion: Moving Apps From Development to Sandbox](https://kiweely.com/blog/workday-extend-graph-api-and-apphub-promotion)

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