---
title: "AMD vs PMD in Workday Extend, for Beginners — Kiweely"
description: "AMD is the app-level map of routes, flows, and data providers. PMD is one page. The business object is a third file, and it is not either of them."
url: https://kiweely.com/guides/workday-extend-amd-vs-pmd-beginners
---

# AMD vs PMD in Workday Extend, for Beginners

In Workday Extend, the AMD declares data providers, task routes, flows, and app properties. A PMD draws one page and calls those providers. Business objects, security domains, and other model files are separate and follow the weekly update once you leave Development.

-   **Checked** against Workday on November 16
-   Applies to **Workday Extend**
-   6 min read
-   Published November 16
-   By Kiweely

AMD and PMD are both presentation metadata, and they do different jobs. The app metadata file (AMD) is the map of the app: which REST services pages may call, which URL opens which page, how pages chain into a flow, and which custom properties other components can read. A page file (PMD) is one screen: the widgets, the data bindings, and the inbound and outbound endpoints for that screen.

Neither file is the data model. A business object is a model component. It stores app data. If a prompt or a tutorial says “put the fields on the page,” the fields still have to exist on the business object, the route still has to exist in the AMD, and the widgets still have to exist in the PMD. Beginners usually edit one of those three and expect the other two to follow.

## The three files people mix up

| File | What it decides | What it does not decide |
| --- | --- | --- |
| AMD (`.amd`) | Data providers, task routes, flows, custom app properties, universal footer pod reference | The widgets on a page, or the fields stored on a business object |
| PMD (`.pmd`) | Layout, widgets, bindings, and the endpoints that page calls | The base URL of a REST service (that key lives in the AMD), or who may open the page (that is a security domain) |
| Business object (`.businessobject`) | The stored fields and the default security domains | How the page looks |

A site metadata file (SMD) sits beside the AMD. It holds authentication types and custom error pages. Pods (`.pod`) and scripts (`.script`) are reusable page pieces. Cards in page configuration are a different thing from cards on the Workday home page. All of those presentation files have a published size limit of 100 KB each.

`applicationID` inside the AMD is read-only. App Builder and the IntelliJ plugin both refuse a change to it. Do not ask an assistant to “fix” the application id. Change the app name and reference ID only when you create or copy the app, and remember that a reference ID cannot be reused even after you delete the app.

## How a page actually calls Workday

Data providers are the REST services the app may call. They live in the AMD `dataProviders` array as a key and a base URL. Workday’s own sample uses the Staffing service:

```
"dataProviders": [
  {
    "key": "workday-staffing",
    "value": "https://api.workday.com/staffing/v1/"
  }
]
```

Workday recommends HTTPS in that base URL. The PMD does not repeat the host. An inbound endpoint on the page points at the key:

```
"endPoints": [
  {
    "name": "worker",
    "baseUrlType": "workday-staffing",
    "url": "workers/me"
  }
]
```

An outbound endpoint uses the same `baseUrlType` and can build the rest of the path with a PMD script, as in Workday’s check-in sample (`workers/` plus a page variable). If the page calls a host the AMD never declared, the page is wrong even when the widget JSON looks fine.

When you create a page, App Builder adds a task. The default `routingPattern` is the page id. Override it when the URL should not match the id. Workday’s charity sample shows the split:

| Task id and page id | Routing pattern | What the user opens |
| --- | --- | --- |
| `donateConfirm` | `/donateConfirm` | A confirmation page at that path |
| `createCharity` | `/charities/create` | A create page whose URL is not the page id |
| `donate` | `/donate/{charityId}` | A page that reads `charityId` from the URL |

The task id, the `page.id`, and the page name need to match. A generated app that “has the page” but has no task, or has a task whose page id points at a renamed file, will not open.

Flows are also AMD. A flow strings pages into steps and can branch on runtime conditions. The flow does not draw the step. Each step is still a PMD.

## What a new page contains before you add anything

A new Extend page has a presentation subschema. Workday says the default tags are:

-   **Title**, the headline at the top.
-   **Body**, the root section.
-   **Section**, inside the body, arranged in horizontal or vertical columns.
-   **Text**, a plain-text message.
-   **Footer**, with a rich-text tag that can contain HTML.

A widget is a JSON object with a `type`, a unique `id`, attributes, and optional event scripts in `<% %>`. The `type` is the tag name. An attribute can be a static value, a script, a child tag, or an array of children. That is the whole PMD model. There is no separate template language beside this JSON.

Presentation components live in the `presentation` folder. Pods go in `presentation/pods`. Scripts go in `presentation/scripts`. Model files, including business objects, business processes, security domains, attachments, tasks, and reports, live in the `model` folder. Orchestration files are a third folder. Do not store a PMD under `model` or a business object under `presentation` and expect the tools to treat them as the same kind of component.

## A worked check after an assistant edits both files

Use this when Developer Agent, or any editor, touches a page and the app metadata in one turn. The nomination tutorial tells you to do the AMD half explicitly.

1.  Open the AMD. Find `tasks`. Confirm a task exists whose `page.id` is the page you just accepted.
2.  If this page should be the landing page, `routingPattern` is `/`. If it should be a create page, the pattern is the path you will actually open, not merely the file name.
3.  Open the PMD. Confirm the endpoint `baseUrlType` is a `key` that exists in `dataProviders`, or a business-object API the page is allowed to call. Do not leave a full host inside the PMD when the AMD is supposed to own the base URL.
4.  If the page collects fields, confirm those field names exist on the business object. The PMD label “Employee Name” does not create the `employeeName` field.
5.  Validate in App Builder before Save to App Hub. Schema, semantic, and syntax checks do not all run as you type.

## Failure modes

-   **Preview shows the page, the deployed app opens another.** The task route still points at the old page id. Preview can open a page directly. The app URL uses the AMD.
-   **The endpoint fails and the widgets look correct.** `baseUrlType` does not match a data-provider key, or the provider still uses a non-HTTPS base URL against Workday’s recommendation.
-   **You edited `applicationID`.** That property is read-only. Revert it. The reference ID of the app is assigned when the app is created and is not a PMD setting.
-   **The page file will not save and it is huge.** Presentation component files are limited to 100 KB. Move repeated widgets into a pod and repeated script into a `.script` file.
-   **You “fixed” stored data by editing the PMD.** Stored fields, security domains, and business-process routes are model components. Once a version that contains them has deployed, Workday says you cannot remove those model components. Changing a label on the page does not remove the field.

## Frequently asked questions

### Is the AMD the data model?

No. The AMD is presentation metadata for providers, routes, flows, and app properties. The data model is the business object in the model folder. A page can call that object’s API only after the object exists and the page endpoint is wired.

### Does every page get a route automatically?

App Builder adds a task when you create a page, with the page id as the default routing pattern. A generated page can still arrive with a mismatched id. Check `tasks` after you apply a diff. You can override `routingPattern` when the URL should differ from the page id.

### What is the SMD for, if the AMD already exists?

The SMD holds site-level authentication types and custom error pages. It is not a second AMD, and it is not a page.

### Where do reusable bits go?

Pods hold reusable widgets. Scripts hold reusable PMD script. Both are presentation components, both count toward the 100 KB file limit, and both are referenced by pages rather than copied into every PMD.

## Sources checked

-   [Concept: Extend App Metadata](https://developer.workday.com/documentation/qdr1547677184237/ConceptExtendAppMetadata)
-   [Concept: Presentation Components](https://developer.workday.com/documentation/kfa1528474007875/ConceptPresentationComponents)
-   [Getting Started with Extend Presentation Components](https://developer.workday.com/documentation/GUID-0211143b-4859-4f84-9cf9-4bf3d355fb19/GettingStartedwithExtendPresentationComponents)
-   [Concept: Extend App Components](https://developer.workday.com/documentation/kwv1612374098305/ConceptExtendAppComponents)
-   [Concept: Workday Extend Plugin for IntelliJ](https://developer.workday.com/documentation/mpc1559620650152/ConceptWorkdayExtendPluginforIntelliJ)

## Related guides

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

-   [### Workday Extend Model Components and the Weekly Update Business objects, security domains, attachments, processes, reports, and tasks are model components. Development deploys immediately. Other tenants get model changes on Friday night, and only if you promoted before Thursday. Deployed model components cannot be removed.](https://kiweely.com/guides/workday-extend-model-components-weekly-update)
-   [### The Validate and Deploy Proof Ladder for Workday Extend Preview and validate before a tenant sees anything. Save to App Hub writes a build. Deploy reaches a development tenant only. Promote one level at a time. Model components still wait for the weekly update. Orchestrations validate in Orchestration Builder.](https://kiweely.com/guides/workday-extend-validate-deploy-proof-ladder)
-   [### Your First Workday Extend Validation Error from AI Validate checks schema, semantics, and syntax, and some of those checks do not run as you type. A generated diff can still fail. Model error codes name the limit you hit. Reject a bad diff instead of stacking repairs, and do not deploy over a red validate.](https://kiweely.com/guides/first-workday-extend-validation-error-ai)
-   [### Build Your First Workday Extend App with Developer Agent Developer Agent proposes Extend components in App Builder. You still create or accept the business object and security domain, apply the diff, validate, deploy to a development tenant, and activate the domain security policy yourself.](https://kiweely.com/guides/first-workday-extend-app-developer-agent)

### More guides on Extend apps and pages

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

-   [Security Domains for Your First Workday Extend App](https://kiweely.com/guides/first-workday-extend-app-security-domains)
-   [Is there an AI tool that can build, validate and deploy Workday Extend apps?](https://kiweely.com/guides/ai-tool-build-validate-deploy-workday-extend-apps)
-   [AI Browser Testing for Workday Extend Pages: Grids, Attachments, and BP Steps](https://kiweely.com/guides/ai-browser-testing-workday-extend-grids-attachments-bp)
-   [Workday Extend App Preview Is Not Proof the App Works in the Tenant](https://kiweely.com/guides/workday-extend-app-preview-is-not-tenant-proof)
-   [How to Map Control Fields and Related Business Objects in Workday Composite Subreports](https://kiweely.com/guides/workday-composite-report-control-fields-business-object-swap)
-   [Workday Lookup Related Value (LRV) Explained: Crossing Business Objects Without Blank Rows](https://kiweely.com/guides/workday-lookup-related-value-lrv-calculated-field)
-   [Fixing Graph API DataSourceFilter Is Inaccessible Errors and Blank processingWorker Fields When Proxying](https://kiweely.com/guides/workday-graphql-datasourcefilter-inaccessible-processingworker-proxy)
-   [Clearing Single-Instance Relationships to Null and Binding createdBy with graph:createId() in Graph API](https://kiweely.com/guides/workday-graphql-clear-single-instance-null-graph-createid)

### From the blog on Extend apps and pages

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

-   [How do you test a Workday Extend app end to end?](https://kiweely.com/blog/test-workday-extend-app-end-to-end)
-   [When a Workday Custom Report Is Enough vs. When You Need Prism or an Extend App](https://kiweely.com/blog/when-workday-custom-report-is-not-enough)
-   [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)

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