Skip to content
KiweelyKiweelyKiweely

How do I fix “Failed to generate WUL from PMD snippet” in Extend?

Failed to generate WUL from PMD means the snippet will not compile—usually a bad structure or binding shape. Shrink the widget, prove it with a literal, then match the real endpoint response.

  • Checked against Workday on
  • Applies to Workday Extend Presentation Components (PMD)
  • 2 min read
  • Published
  • By Kiweely
On this page

Failed to generate WUL from PMD snippet means Workday could not compile the presentation model into the form the page renders. The trailing “A failure occurred while processing your request. Contact your administrator.” text is a generic wrapper. It does not, by itself, mean a tenant permission problem.

What is going wrong

Presentation Components resolve binding and dynamicBinding attributes when the page loads. Inbound endPoints supply the data those bindings read. If a widget attribute expects one shape—for example a single object—and the binding supplies another—for example an array—or the snippet is structurally invalid, compile fails for the whole snippet. The message does not point at a line number.

Workday’s displaying-data concept distinguishes:

  • binding — resolved on initial load only
  • dynamicBinding — resolved on load and able to change with user interaction on an edit page

Either kind fails compile when the value it resolves to is the wrong type for the attribute.

Isolate the bad attribute

  1. Note the last widget or attribute you changed. Start there.
  2. Cut that widget back to a minimal version that still has the required properties. Confirm the page compiles.
  3. Add attributes back one at a time until compile breaks again.
  4. Replace the failing dynamic binding with a hard-coded literal in the shape the attribute expects. If that compiles, the widget is fine and the binding or data is not.
  5. Call the endpoint outside the page (or log its payload) and compare the real response to what the attribute needs. An array where a single object is required—or the reverse—is a common mismatch.
  6. Fix the binding expression or the endpoint mapping, restore the binding, and validate again.

Keep a known-good shape nearby

For complex attributes, keep a static example in the app that is known to compile. When a later change fails WUL generation, diff against that example before rewriting the whole page. Confirm each inbound endpoint declares name, baseUrlType, and url, and that scripts reference the endpoint by that name.

This error is different from failed to resolve a definition, which means a named pod, include, or endpoint is missing. It is also different from a runtime Internal Server Error on submit, which is an outbound call failure after the page already compiled.

Kiweely Vine can validate Extend presentation components and help you bisect a PMD snippet when you are working in a connected project.

Frequently asked questions

Does “Contact your administrator” mean I lack tenant permission?

Usually no. That text is a generic wrapper around a PMD compile failure. Fix the snippet structure or binding shape first.

Why is there no line number in Failed to generate WUL?

Workday reports the failure for the snippet as a whole. Bisect by cutting the last widget back to a minimal form, then re-adding attributes.

When should I use a literal instead of a binding?

Use a hard-coded value in the shape the attribute expects to prove the widget compiles. Then replace it with a binding only after the endpoint returns that same shape.

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.