Failed to resolve a definition in an Extend PMD means the page names something Presentation Components cannot find when the page loads: a podId, an included script module, an endpoint alias, or another presentation reference that was renamed, removed, or never deployed. The app can still deploy. The page fails when it tries to resolve that name.
What Workday resolves on a PMD
| Reference | What Workday requires |
|---|---|
Referencepod tag podId |
What Workday requiresA .pod file whose podId matches; Workday replaces the tag with the pod template before inbound fetches |
Referenceinclude script modules |
What Workday requiresFiles that exist under presentation/scripts and are listed in the PMD include array |
ReferenceendPoints entries |
What Workday requiresEach inbound endpoint needs at least name, baseUrlType, and url so the page can bind to name |
| ReferenceWidget and binding names | What Workday requiresIds and endpoint names the page script and attributes actually define |
Workday’s pod reference states that during preprocessing, Presentation Components replace a pod tag with the pod template and substitute parameters. That replacement happens before inbound endpoints fetch data. A missing or mistyped podId therefore fails early as an unresolved definition, not as a quiet empty widget.
Fix steps
- Copy the unresolved name from the error exactly, including capitalization.
- Search the app for that string. Check whether it was renamed, deleted, or only exists in a branch that never deployed.
- If it is a pod, open the
.podfile and confirmpodIdmatches the PMD’spodtag. Pod files live in the app’s pods folder and have a 100 KB size limit. - If it is a script module, confirm the filename appears in the PMD
includearray and exists underpresentation/scripts. Pods cannot declare their ownincludeorscript; only the calling PMD loads modules. - If it is an endpoint, open the PMD (and any pod that declares
endPoints) and confirm thenamespelling. Endpoint aliases are how the page binds data; a rename in one place without the other leaves a dangling reference. - Redeploy the app, then hard-refresh the page. A cached page can keep showing the old failure after a fix.
Prevent the next rename from breaking pages
Adopt one naming convention for widgets, pods, and endpoints. When you rename, search the whole app—including .pod files, which can declare their own endPoints. Load every page once in a non-production tenant after deploy. That catches unresolved definitions before users do.
Kiweely Vine can open the PMD and search for the unresolved name in your project when you are building or validating an Extend app on a connected machine.
Frequently asked questions
Why does my Extend page fail to resolve a definition after deploy?
The PMD still names a podId, endpoint, script module, or widget that is not in the deployed app. Correct the reference or restore the missing file, redeploy, and reload.
Can a wrong podId cause failed to resolve?
Yes. Workday says a pod with the specified podId must exist in the app’s pods folder. The PMD pod tag is replaced with that template before data fetch.
Is this the same as Failed to generate WUL from PMD?
No. Failed to resolve is a missing or mistyped reference at render time. Failed to generate WUL is a compile-time failure turning the PMD snippet into the page representation.