Workday — From Zero to Hero

What Is Workday?

Workday is a cloud-based enterprise software platform that runs Human Capital Management (HCM), Finance, Payroll, and Planning for thousands of organizations worldwide. Unlike older "ERP" systems (SAP, Oracle EBS, PeopleSoft), Workday was built from the ground up as a single object-oriented database, accessed through a web browser, with one unified data model shared across HR and Finance.

The Tenant Concept

Every customer of Workday is given one or more tenants. A tenant is your private, isolated copy of Workday — your data, your configuration, your security. You will typically see three:

High-Level Architecture

The Workday Modules You'll Encounter

Navigation Basics

Workday is driven by three things you'll use every minute:

The Workday Data Model — Business Objects

Workday is object-oriented. Everything — every worker, every position, every cost center, every journal line — is an instance of a Business Object. If you've used Salesforce, think of Business Objects as the equivalent of "tables" — but smarter, because they know how they relate to other objects.

Object vs. Instance

The 12 Business Objects You Must Know

Worktags — the Bridge Between HCM and Finance

Worktags are the secret sauce of Workday. A Worktag is a tag (like a hashtag) that gets attached to almost every transaction — an expense, a payroll cost, a journal line. They classify where a cost lives without bloating your GL chart of accounts.

How Objects Relate — The Core HCM Map

Understanding object relationships is the single most important skill in Workday reporting. Pick the wrong starting object and you'll either get duplicate rows or miss data. Here is the map you must memorize.

The Core HCM Relationship Map

Cardinality — One-to-Many vs Many-to-One

Effective Dating — the Workday Time Machine

Almost every object in Workday is effective-dated. That means Workday stores not just what something is, but when it became that. You can ask "What was the org chart on December 31?" and get a correct answer.

Data Sources — Where Reports Start

A Data Source is a pre-built query that returns a set of instances of a Business Object, often filtered for performance or security. Every report in Workday starts by choosing a Data Source. Choose well and the rest of the report is easy. Choose poorly and you'll fight the report forever.

Anatomy of a Data Source

Primary vs. Related Business Objects

The Primary BO determines the grain of your report — what one row represents. Related BOs are reached by "dot-walking" from the primary (e.g., Worker → Primary Position → Job Profile → Job Family).

The 10 Data Sources You'll Use Most

Indexed Data Sources — When You Need Speed

If a data source name ends in (Indexed), Workday has pre-computed it. They run dramatically faster but have one rule: any filter you add must use indexed fields. Otherwise the index is bypassed and you lose the speed benefit.

Fields — The Building Blocks of Reports

A Field is one column on a Business Object. When you build a report, you're really just picking which fields of which business object to display, filter, sort, and group by. Workday gives you thousands of fields out of the box.

Field Types

Single-Instance vs Multi-Instance

Dot-Walking — Reaching Related Fields

"Dot-walking" is Workday slang for following reference fields. If the primary object is Worker and you want the worker's manager's email, you walk: Worker → Manager → Work Email. In the field picker this looks like "Manager > Work Email".

Two Field Lists You Need to Know

Calculated Fields — Workday's Power Tool

A Calculated Field is a custom field defined by a function. You build them once, then use them in any report, dashboard, integration, or business process. They are the difference between a junior Workday user and a senior one.

The Calculated Field Workflow

The 12 Function Types You Will Actually Use

Worked Example 1 — Tenure in Years

Function: Date Difference
Business Object: Worker
Start Date: Worker → Continuous Service Date
End Date: Today (or report's Effective Date)
Output Unit: Years
Output Type: Numeric (1 decimal)

Result for Jane Doe (hired 2021-04-12, today 2026-06-03):
  5.1 years

Worked Example 2 — Tenure Bands (IF/THEN/ELSE)

Function: Evaluate Expression
Business Object: Worker
Return Type: Text

When Tenure (Years) is less than 1      → "0–1 yr (New Hire)"
When Tenure (Years) is less than 3      → "1–3 yrs"
When Tenure (Years) is less than 5      → "3–5 yrs"
When Tenure (Years) is less than 10     → "5–10 yrs"
Otherwise                                  → "10+ yrs (Tenured)"

Worked Example 3 — Manager Email (Lookup Related Value)

Function: Lookup Related Value
Business Object: Worker
Lookup Field: Manager  (reference field on Worker)
Return Field: Work Email Address

Result: Jane Doe → looks up her manager (Mark Lee) → returns
        mark.lee@company.com

Worked Example 4 — Full Name + ID (Concatenate Text)

Function: Concatenate Text
Business Object: Worker
Inputs:
  1. Worker → Last Name
  2. ", "
  3. Worker → First Name
  4. " ("
  5. Worker → Employee ID
  6. ")"

Result: "Doe, Jane (10042)"

Best Practices

• Name with a prefix — e.g. "CF_Tenure_Years". Makes them easy to find vs. delivered fields.
• Reuse, don't rebuild — before creating a new CF, search the tenant. Someone probably built it already.
• Build on Worker when possible — the most reusable.
• Avoid nested calculated fields when speed matters — they cascade and slow large reports.
• Document the purpose in the Description field of every CF you create.

Report Types — Choosing the Right Tool

Workday gives you six report types. Picking the right type at creation time matters — you can't easily convert between them later.

The Six Report Types

Decision Tree — Which Type?

Standard vs Custom Reports

Build Your First Report — Step by Step

The Recipe

1. Search "Create Custom Report" in the global search bar. Open the task.
2. Name the report. Use a convention like RPT_HCM_Headcount_by_CostCenter_v1. Future you will thank you.
3. Report Type: Advanced.
4. Data Source: "All Active Employees" (Primary BO = Worker, built-in filter = Active = TRUE).
5. Optional Filter Field: leave blank — we'll add filters in step 7.
6. Columns tab — add fields in this order:
   • Worker → Employee ID
   • Worker → Full Name
   • Worker → Primary Position → Job Profile → Job Title
   • Worker → Cost Center (via Worktags) → Cost Center Name
   • Worker → Hire Date
   • Calculated Field: CF_Tenure_Years (from Module 6)
   • Calculated Field: CF_Tenure_Band (from Module 6)
7. Filter tab — add: Cost Center → Cost Center Hierarchy → contains → "EMEA" (just so we focus the test set).
8. Prompts tab — promote Effective Date and Cost Center to runtime prompts so end-users can re-slice.
9. Sort tab — sort by Cost Center Name (asc), then Hire Date (desc).
10. Output tab — enable Excel and CSV. Optionally enable a bar chart on Tenure Band.
11. Share tab — share with the security group "HR Analysts". Mark "Run as the user who runs the report" for proper row-level security.
12. Save & Run. If it returns in < 5 seconds for 1,000+ rows, you have a healthy report.

What Each Tab Actually Controls

Run-Time Prompts vs Filters — the Single Most Confused Topic

Advanced Reporting — Matrix, Composite, Performance

Matrix Reports — Pivots Inside Workday

A Matrix is a pivot table. You pick one or two grouping fields and one or more measures (count, sum, average). Workday produces a cross-tab plus a drill-down to the underlying detail.

Composite Reports — When You Need Multiple Sections

A Composite report stitches together several "sub-reports" (each one usually a Matrix) into a single document. Classic use case: a one-page HR Operations Dashboard with sections for Headcount, New Hires, Terminations, Open Reqs, and Cost Center Spend — all in one PDF.

Sub-Filters & Sub-Totals

Sub-Filter: filters at the related-object level. Example: from Worker, return only those Pay Results where pay period is current quarter (rather than all history). Sub-Totals: on Matrix and grouped Advanced reports, you can add row/column sub-totals, averages, and percent of total.

Performance Tuning Checklist

• Use an indexed data source if available.
• Filter early — push your most selective filter to the very top of the Filter tab.
• Avoid calculated fields in Filter — they prevent index use.
• Limit dot-walks to ≤ 3 hops where possible.
• Schedule heavy reports overnight; deliver via Drive or email.
• Use Report Performance task to inspect long-running reports.
• Cache wisely — repeat-run reports benefit from server cache; first run is always slower.

Security & Extracting Data (to Power BI & Beyond)

Security in Two Layers

Four Ways to Get Data Out of Workday

The RaaS → Power BI Pattern

RaaS Setup Checklist

1. Build the source report as an Advanced report. Avoid Matrix/Composite — they don't expose clean tabular data.
2. Enable Web Service in the report's Advanced tab. Workday generates a unique URL.
3. Create an Integration System User (ISU) with a strong password and an Integration System Security Group (ISSG).
4. Grant the ISSG the minimum domain access needed (data scopes only — not modify rights).
5. Test the URL in a browser with the ISU credentials — confirm you get XML/JSON.
6. In Power BI Desktop: Get Data → Web → paste URL + Basic auth. Use Power Query to flatten.
7. Publish + schedule refresh via an On-Premises Data Gateway or service principal.

When to use Prism instead of RaaS

If your dataset is > ~250k rows, refreshes more than hourly, or needs to be blended with non-Workday data (Excel, SQL Server, Salesforce), the right answer is usually Prism Analytics. RaaS is excellent for < 100k row extracts; Prism scales to millions.