Workday errors in plain English.

Submit an Error

Extend PMD App Attribute Reference Fails With Unknown Variable

✓ Verified Workday Extend 5 lookups
The error Page Error Internal Server Error. [F5S|********|********] Unknown Variable found: attrstore.tenantPassword Script Excerpt: attrstore.tenantPassword

What does "Extend PMD App Attribute Reference Fails With Unknown Variable" mean in Workday Extend?

An Extend app page will not render and reports an unknown variable for an app attribute referenced as attrstore.<name>. The app can see its attribute store, but the specific key you asked for does not resolve in this tenant.

Quick fix

Output <% attrstore %> on its own to prove the store is bound, then replace the key in your script with the exact Alias shown on the app's attribute list and redeploy.

Permanent fix

Treat app attributes as deploy-time configuration rather than runtime data. Keep one canonical list of alias names, reference attributes only through those aliases, set a value in every environment the app is promoted to, and redeploy whenever the attributes file changes.

Troubleshooting

  1. Render the whole store first by outputting <% attrstore %> on the page. If that prints an object, the store is bound and the problem is the individual key rather than the plumbing.
  2. Compare the name in your script against the Alias column on the app's attribute list, not the Attribute column. PMD resolves the alias, and the two columns are edited independently.
  3. Confirm the attribute has a value set for the environment you are testing in. Attribute values are per environment, so one defined in a development tenant with no value in IMPL resolves to nothing.
  4. Redeploy the app after any change to the attributes file or the app configuration. The store is bound at deploy time, so an attribute added since the last deploy does not exist in the running app.
  5. Check the version of the Extend plugin or CLI that generated your attributes file. An older plugin can emit a file missing keys the current app configuration expects.
  6. If the name, alias, value and deploy are all correct, retry once after a short wait before opening a case. This error has been observed clearing on its own when the tenant side of the attribute store was at fault rather than the app.
Was this helpful?

Related errors

Workday Extend PMD Validations Tag Fails with Unknown Property Found Error After Switching from EL to PMD Scripting Workday Extend Extend Edit Page Returns a Bare Internal Server Error on Submit Workday Extend Extend PMD Endpoints Never Register Because the Key Is Lowercase Workday Extend Extend PMD 'Unknown Variable' Error When Clearing a Widget Value With Double Quotes Workday Extend Extend App Fails to Download on Windows After Being Deployed From Mac Workday Extend Custom Validation Error Not Displayed in Extend App (PMD Binding Typo)