Analytics Catalog/Workday/Calculated fields
Explore the catalogModulesExtraction patternDelivered vs ownedData sourcesData CloudWorker
Workday · Spine · Editorial

The logic that cannot leave

Years of definitions accumulate as calculated fields: tenure bands, bonus eligibility, the real termination flag. Workday computes them at report runtime and stores none of them. Then the extraction project starts, and the logic stays home.

RuleInventory your calculated fields before choosing an extraction path. The list decides how much logic you are carrying versus rebuilding.
Neverrebuild a definition silently. Every rebuilt field gets a test comparing it to the tenant’s value on the same rows.
◆ What a calculated field islogic at runtime, not data at rest.

A calculated field is a formula defined inside the tenant: take hire date, compare it to today, sort the result into bands. When a report runs, the value is computed, displayed, and discarded. Nothing is stored. Over years, hundreds of these accumulate, and together they quietly become the company’s definitions of tenure, eligibility, and status.

That works until the data needs to leave. Reports return the computed values. So do WQL queries, because Workday gives every calculated field a WQL alias, delivered or custom. What never leaves is the formula, which exists only in a tenant screen.

Calculated field computed at runtime Report or WQL output values carried out Owned model logic rebuilt as code The formula stays in the tenant, runs only there
The values travel with any extract that asks for them. The formula runs only in the tenant, which is why the owned model rebuilds it.
◆ Which paths carry the logicvalues travel, formulas do not.
Path outCalculated fields?The consequence
Report extractionYes, the computed values ride along in the output.The values arrive without their formulas. You have answers you cannot explain, at report caps covered on the extraction pattern.
Query languageYes, as values. Workday creates a WQL alias for every calculated field, delivered or custom.The scalable path still arrives without the definitions, and fields from Global business objects stay out of its reach, though report extraction can read them.
Web servicesNo. Objects and stored fields only.Same stranding, object by object.
Zero-copy shareStored data, as tables. Runtime report logic is not a table.Even the future pipe carries data, not definitions. See Data Cloud.

The trap has a shape: every path carries answers, and none carries the definitions. Teams discover it mid-migration, when the new pipeline lands rows that no longer match the reports everyone trusts, because the trusted numbers came from formulas nobody wrote down.

◆ The rebuildonce, as tested code you own.

The durable answer is to treat calculated fields as a specification and rebuild them once in the warehouse, as versioned, tested transformations. The formula that lived in a tenant screen becomes code in your repository, with a test proving it matches the tenant on the same rows.

-- a tenant tenure-band field, rebuilt as owned logic
SELECT worker_id,
       CASE
         WHEN months_between(current_date, hire_date) < 12  THEN 'Under 1 year'
         WHEN months_between(current_date, hire_date) < 60  THEN '1 to 5 years'
         ELSE 'Over 5 years'
       END AS tenure_band
FROM dim_worker
WHERE is_current

The landed facts this logic rebuilds against are mapped on the Workday spine model.

Rebuilt logic upgrades on the way over. It gains history, because the model computes the band as of any snapshot date, which the runtime field never could. It gains a test. And it gains an audience, because a definition in code can be read, reviewed, and reused by every report downstream, instead of living in one report’s configuration.

Use case
Problem
Years of business definitions live as calculated fields whose formulas never leave the tenant, so pipelines land rows that no longer match trusted reports.
What we build
The field inventory, then each definition rebuilt once as versioned, tested transformations in your warehouse.
What you get
Logic that matches the tenant provably, gains history and review, and serves every downstream report instead of one.
How many definitions live only inside your tenant?
We inventory the fields, rebuild the logic as tested models, and prove the match.
Talk to us
Terms on this page
calculated field
A formula defined in the tenant, computed at report runtime, never stored.
data source
The population a report or query reads. Its fields include the calculated ones.
query language
Workday’s structured query path over its data sources. Scales well, returns calculated values through aliases.
WQL
Workday Query Language, the query language named above.
web services
The object-by-object programmatic path. Stored fields only.
runtime
The moment a report executes. Where calculated values briefly exist.
versioned
Kept in source control, with history and review.
specification
A definition treated as the requirement code must match.
snapshot date
The as-of date a model computes against. Runtime fields know only today.