---
title: "Why Workday RaaS Output Differs From Interactive Runs"
description: "Why a Workday custom report returns different rows or blank fields via RaaS: ISU security domains, constrained groups, prompt defaults, and Pacific Time rules."
url: https://kiweely.com/blog/why-workday-reports-differ-between-run-and-raas
---

# Same Report, Different Rows: Why a Workday Custom Report Changes Output When Enabled as RaaS

A Workday custom report changes output over RaaS for three reasons: the Integration System User has different domain or organization security than the person clicking Run, runtime prompts fall back to undefined or static defaults, or Pacific Time shifts effective-dated boundaries.

-   By Kiweely
-   November 13
-   7 min read

When a Workday custom report returns one row count in your browser and a different row count (or blank columns) when called as a Report-as-a-Service (RaaS), the report definition itself has not changed. Either the **Integration System User (ISU)** calling the endpoint has different domain or organization security than you do, a runtime prompt fell back to a hidden default, or the ISU’s mandatory **Pacific time zone** evaluated effective-dated records on a different calendar day.

Nearly every integration developer hits this puzzle at least once: a functional analyst builds an advanced custom report, verifies 1,420 active workers on screen, checks **Enable As Web Service** on the **Advanced** tab, and hands over the JSON URL. Ten minutes later, the downstream middleware receives 0 rows, 980 rows with missing compensation fields, or 4,300 rows covering countries the analyst never intended to include.

## Diagnostic Matrix: Interactive Run vs. RaaS Output Mismatches

Before editing filters on the custom report, match the discrepancy you are seeing to the exact Workday mechanism that differs between browser sessions and web service calls:

| Observed Discrepancy | Root Cause in Workday | Exact Check to Confirm |
| --- | --- | --- |
|  **Specific columns are blank or missing in JSON/XML** | ISU’s security group lacks `Get` / `View` access to the domain securing those fields or an underlying calculated field | Run **View Security for Securable Item** on the missing report field and check **Activate Pending Security Policy Changes** |
|  **RaaS returns 0 rows or a partial subset of rows** | Constrained ISSG lacks organization scope, or a report filter references a field the ISU cannot read | Compare the interactive user’s security groups against the ISU’s **Integration System Security Group (ISSG)** |
|  **RaaS returns *more* rows than the report author sees** | Author tested under a constrained role (e.g., *HR Partner*), while the ISU belongs to an **Unconstrained** ISSG | Check whether the report relies on implicit role security instead of an explicit filter on the **Filter** tab |
|  **Effective-dated hires or terms differ around midnight** | ISUs always retrieve data in **Pacific Time**, whereas UI users evaluate in their account’s local time zone | Pass an explicit effective date in the RaaS URL or check **Use Pacific Time Zone for Effective Moment** on the **Prompts** tab |
|  **Prompt criteria seem ignored over HTTP** | Query parameter uses display label instead of **Label For Prompt XML Alias**, or omits `%21WID=` instance formatting | Open **Related Actions > Web Services > View URLs** on the report and inspect the generated query string |
|  **CSV column order or multi-instance formatting shifts** | CSV drops **Group Column Headings** ordering; **Simple XML** joins multi-instance values with semicolons | Switch integration consumers to **JSON** or **Workday XML** and verify schema via **Web Service > View WSDL** |

## Cause 1: Sharing Does Not Override Field or Filter Security

Checking **Share with specific authorized groups and users** on the **Share** tab grants your ISU permission to *execute* the report definition, and nothing more. As Workday’s report security model enforces on every run, sharing a report never overrides security on the **Report Data Source (RDS)**, the **RDS Filter**, or individual **Report Fields**.

Two silent behaviors catch teams by surprise here:

1.  **Silent column suppression and broken filter fields.** When an ISSG has access to the RDS (for example, *Workers for HCM Reporting*) and the chosen RDS filter, the RaaS HTTP call succeeds with `200 OK`. If Column 7 displays `Total Base Pay` or a custom calculated field that traverses a compensation or national ID domain where the ISSG has no `Get` or `View` permission, Workday simply omits or blanks that field in the payload. Worse, if the **Filter** tab filters on that secured calculated field (for example, `Calculated Eligibility Flag = true`), the field evaluates as empty for the ISU and drops matching rows altogether. See our guide to [fixing empty shared custom reports](https://kiweely.com/guides/workday-custom-report-sharing-security-empty) for step-by-step domain checks.
2.  **Constrained author vs. unconstrained ISU.** Consultants often test reports while proxied as a regional *HR Partner* whose constrained role-based security group automatically scopes results to EMEA supervisory organizations. Nobody adds an EMEA filter on the **Filter** tab because the preview already looks right. As soon as an unconstrained ISSG calls the RaaS endpoint, Workday returns every worker globally.

## Cause 2: Prompt Defaults and `Label For Prompt XML Alias` Syntax

When you click **Run** in the browser, Workday pauses on the prompt screen, pre-populates user-contextual defaults, and lets you pick organizations or checkboxes interactively. An ISU calling a REST or SOAP RaaS URL never sees a prompt screen: Workday either binds the exact query parameters on the URL or falls back to whatever sits on the **Prompts** tab under **Default Value** (*Specify default value* or *Determine default value at runtime*).

If **Populate Undefined Prompt Defaults** left a prompt blank, or if a dynamic default like *Current User’s Supervisory Organization* resolves to nothing for a workerless ISU account, the filter behaves completely differently than it did in your browser.

Even when developers pass prompt parameters on the URL, hand-typed query strings frequently fail two Workday RaaS formatting rules:

-   Parameter names must match the **Label For Prompt XML Alias** on the **Prompts** tab, not the human-readable prompt instruction.
-   Prompts expecting Workday object instances require `!WID` (`%21WID`) notation, with multiple WIDs separated by `!`:

Fails

```
# Wrong: passes human label and plain-text organization name; Workday ignores or rejects the filter
.../customreport2/acme/isu_hr_sync/Org_Headcount?Supervisory Organization=Engineering&Include Subordinates=true&format=json
```

Works

```
# Right: uses exact Label For Prompt XML Alias values, %21WID=<WID> instance syntax, and 1/0 boolean
.../customreport2/acme/isu_hr_sync/Org_Headcount?Organization%21WID=cb550da820584750aae8f807882fa79a&Include_Subordinate_Organizations=1&format=json
```

Instead of guessing parameter syntax, always open the report’s related actions menu, select **Web Services > View URLs**, supply sample prompt values, and copy the exact URL Workday generates. Also verify that the report owner’s Workday username does not contain a backslash (`\`) character, which breaks `GET` RaaS execution.

## Cause 3: The Pacific Time Zone Rule on ISU Accounts

One of the hardest bugs to reproduce happens only for a few hours each night. A payroll or provisioning integration runs at 02:00 UTC (10:00 PM EDT / 07:00 PM PDT) on the first of the month, and misses every hire effective on the 1st. When an administrator in London or New York runs the exact same report the next morning, every new hire is right there.

Workday documents the underlying rule explicitly in its integration limits: **Integration System User accounts always retrieve data based on the Pacific time zone.**

When a report does not pass an explicit effective date—or uses date fields anchored to `Today` without pinning time zone behavior—an interactive user in London at 02:00 UTC on May 1 runs the report as of **May 1**, while the ISU runs the exact same report as of **April 30** (7:00 PM Pacific).

Aligning Effective Moments Across UI and RaaS

On standard-data-source custom reports, open the **Prompts** tab in **Edit Custom Report** and review **Effective Date** and **Use Pacific Time Zone for Effective Moment** (which can also be applied across reports via **Mass Update Reports to Use Pacific Time Zone for Effective Moment**). Better yet, expose an explicit `Effective_Date` prompt on your [RaaS setup](https://kiweely.com/guides/workday-raas-setup) and have your integration pass `YYYY-MM-DD` deterministically on every call.

## Cause 4: Format-Specific Differences and When to Use WQL Instead

Finally, watch how RaaS serializes the output format you choose (`format=json`, `csv`, `simplexml`, or default `Workday XML`):

-   **CSV output** strips column group headers on advanced reports that use **Group Column Headings**, and the resulting CSV columns may not match the column order in the report definition. Always append `&bom=true` when exporting UTF-8 CSV for Excel consumers.
-   **Simple XML** flattens multi-instance fields on the primary business object into a single semicolon-delimited string, whereas **JSON** and **Workday XML** preserve structured child elements.

If you are building a new integration or Workday Extend app and fighting RaaS owner namespaces, report-sharing drift, or 2 GB RaaS payload caps, compare [RaaS vs. WQL and the Workday REST API](https://kiweely.com/guides/workday-raas-wql-rest) before locking in your design.

In [Kiweely Vine](https://kiweely.com/vine), you do not have to eyeball XML aliases or guess which calculated sub-field an ISU cannot read. Vine inspects the live custom report definition, compares your interactive user’s security domains against the target ISU’s **Integration System Security Group** ([tracing Workday security permissions automatically](https://kiweely.com/blog/tracing-workday-security-permissions-with-an-ai-agent)), and pinpoints the exact domain policy, prompt default, or time zone mismatch causing the row discrepancy before anything touches production. Vine Free is free for your Workday personal developer account and its tenant. Any other tenant needs Vine Personal at $99 a month for one person, or a Vine Team seat at $149 a month.

## Frequently asked questions

### Why does my Workday RaaS JSON or XML omit columns that appear when I run the report in the browser?

Workday secures every report field and calculated field dependency through its own security domain. If the Integration System Security Group assigned to your Integration System User lacks Get or View permission on a field's domain, Workday omits or blanks that field in RaaS output instead of failing the HTTP request.

### What time zone does a Workday Integration System User use when running a RaaS report?

Integration System User accounts always retrieve data in the Pacific time zone. If an interactive user in Europe, Asia, or the US East Coast runs the same report near midnight without passing an explicit Effective Date, their local date can differ from the ISU's Pacific date by one calendar day.

### Can a RaaS endpoint return more rows than an admin or HR Partner sees interactively?

Yes. If the person running the report in the UI belongs to a constrained role-based security group limited to specific supervisory organizations, while the integration uses an unconstrained Integration System Security Group, RaaS returns workers across the entire tenant.

### Why is my RaaS URL ignoring a prompt filter parameter?

RaaS URL parameters must match the exact Label For Prompt XML Alias shown on the Prompts tab of the report definition, and object instance prompts require the %21WID= syntax (or exclamation-separated WIDs for multi-instance prompts) rather than plain text names.

## Read next

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

-   [November 13 ### What Happens When a 50,000-Row Workday EIB Times Out Halfway Through (and How to Batch It Safely)](https://kiweely.com/blog/splitting-large-workday-inbound-eib-loads-safely)
-   [November 13 ### Mass Action Tables Are Quietly Replacing Routine HR EIBs, Except Where Dirty Source Data Lives](https://kiweely.com/blog/when-mass-action-tables-replace-workday-eibs)
-   [November 13 ### Does Workday Data Cloud Kill Outbound RaaS and Studio Extracts? A Consultant’s Reality Check](https://kiweely.com/blog/workday-data-cloud-live-data-query-for-consultants)

### More guides on Integrations and APIs

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

-   [Write Your First Workday Studio AUnit Tests Before Changing the Assembly](https://kiweely.com/guides/write-first-workday-studio-aunit-tests)
-   [How a Workday Sandbox Refresh Affects Registered API Clients and Redirect URLs](https://kiweely.com/guides/workday-api-client-disabled-tenants-sandbox-refresh-impacts)
-   [Register API Client vs. Register API Client for Integrations in Workday](https://kiweely.com/guides/workday-register-api-client-vs-api-client-for-integrations)
-   [Workday API Attachment Rules: File Size Limits, Allowed MIME Types, and Doctor’s Note Uploads](https://kiweely.com/guides/workday-attachment-upload-virus-scan-size-mime-rules-api)
-   [Scoping Workday API Client Functional Areas for Least-Privilege Access](https://kiweely.com/guides/workday-api-client-functional-areas-least-privilege-scoping)
-   [Submitting and Validating Time-Off Requests with the Workday Absence REST API](https://kiweely.com/guides/workday-absence-management-rest-api-request-time-off)
-   [Reading Current Benefits Elections and Dependents Through Workday Self-Service APIs](https://kiweely.com/guides/workday-view-benefits-elections-dependents-beneficiaries-api)
-   [Auditing External API Calls in Workday Sign-On History and Activity Logs](https://kiweely.com/guides/workday-view-api-client-audit-logs-sign-on-history)

## Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.
