---
title: "Custom reports and RaaS for consultants — Kiweely"
description: "How consultants should review AI-suggested Workday custom reports before enabling them as RaaS web services for integrations or outbound EIBs."
url: https://kiweely.com/guides/ai-workday-custom-reports-raas-for-consultants
---

# Custom reports and RaaS when an AI assistant is helping you build them

Advanced and search reports can be enabled as web services. Copy a standard report before you expose it, keep the namespace stable, and use Deployment Agent only to find which custom reports exist in the tenant. You still choose the output type and the security.

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

A custom report becomes a Report as a Service (RaaS) when you enable an advanced or search report as a web service. Workday then exposes results through URLs. The RaaS concept topic lists three consumers: custom Workday Extend applications, integrations to external services such as payroll or benefits providers, and external tools such as Microsoft Excel. Output types on that topic are CSV, GData, JSON, RSS, Simple XML, and Workday XML.

An AI assistant can help you find reports and draft columns. It cannot safely “turn on RaaS” as a side effect. Enabling the web service creates a URL that any tenant account with permission to the report and its data can call. Simple reports do not support the advanced options where web services are configured.

Security for the advanced-options topic is **Custom Report Creation** and **Manage: All Custom Reports** in the System functional area. Do this work in a non-production tenant, then move the report with your usual migration. Deployment Agent, if you use it to discover reports, is itself limited to Implementation, Preview, Sandbox, and Customer Central connected to non-production.

## What to ask before anyone enables the web service

Workday’s sample prompts include a tenant-inspection line for this job:

> In my \[tenant name\] tenant, show me all custom reports created by \[User/Security Group\].

In a tenant that is not Customer Central, the same topic’s shorter form is “in my tenant.” Use it to get a list. Then open each report. Do not enable every report the list returns.

| Question | Where you answer it |
| --- | --- |
| Is this a standard report the integration depends on? | Copy it to a custom report first. If Workday updates the standard report, an integration pointed at the standard report breaks. Enable the custom copy. |
| Advanced or search, or something else? | Web Services Options exist for advanced and search reports. Simple reports have no advanced options. |
| Who will call the URL? | A valid tenant account, plus permission to view the report and the data. Enabling the web service does not bypass security. |
| Does the report owner’s username contain a backslash? | GET requests for a custom report enabled as a web service fail when the owner’s username contains `\`. |
| Will an outbound EIB use it? |  **Enable As Web Service** is what Workday names for outbound EIB use and for external sites. |

## Enable As Web Service, namespace, and what not to change later

On **Edit Custom Report**, open the **Advanced** tab, **Web Services Options**:

| Option | What Workday says |
| --- | --- |
| Enable As Web Service | Use the report in an outbound EIB, or let an external site access it. Access still requires a tenant account and permission to the report and the data. |
| Namespace | Workday generates one. You may change it. Each web-service report should have a unique namespace, but Workday does not enforce uniqueness. If you change the namespace and do not update callers, the request fails. |

The generated namespace format on the RaaS concept topic is:

`urn:com.workday.report/` plus the report name.

The namespace does **not** change when you rename the report or change the owner. That is deliberate, so existing integrations keep working. Treat a namespace edit as an integration change, not a cleanup.

## Pick the output from the caller’s need

| Output | Use when | Trap |
| --- | --- | --- |
| CSV | A spreadsheet, no XML. | Group column headings are dropped. Column order might not match the report definition. For UTF-8, append `&bom=true` so Excel reads the encoding. |
| JSON | A system that requires JSON. | Still a secured URL, not an open feed. |
| Simple XML | Desktop tools that want simpler elements. | Single- and multi-instance fields become strings. Multi-instance values on the primary business object are separated with semicolons. Dates without times lose the time and the GMT offset. You get a Simple XML URL and an XSD URL. |
| Workday XML | REST or SOAP-style integrations that want the literal XML. | Often too heavy for a quick Excel refresh. You get Workday XML, XSD, and WSDL URLs. The concept topic says Simple XML is the better fit for that Excel case. |
| RSS | People subscribe to updates. | The concept topic says users can monitor updates through an RSS feed without logging in to Workday. Confirm that is acceptable before you enable it. |
| GData | Google gadget integrations. | Narrow. Do not pick it as a default. |

**Optimized for Performance** limits prompts to indexed fields on indexed data sources. Clear it when you must show non-indexed fields. **Background Only** forces a background run and still requires security plus a valid URL. **Exclude Execution Link from Search** hides the report from global search so only unconstrained groups such as Administrators or Implementers, or other people with permission, can run it. Use that when the report exists only as a worklet, a composite subreport, or a Worksheets data view.

Temporary reports are scheduled for deletion in 7 days or on a date you set. They are not deleted until someone runs **Delete My Temporary Report Definitions** (or an admin runs **Delete All Temporary Report Definitions**). Do not point an integration at a temporary report.

## Calculated fields on the report

If the AI draft says “add a calculated field,” apply the calculated-field rules before you enable RaaS:

-   Report-specific fields cannot be used on simple reports.
-   You cannot filter discovery boards or Report Writer on fields that return derived instances, such as lookup date rollup.
-   Tenant-wide fields are the ones you can reuse on an EIB or another report. Convert only when **Maintain Calculated Fields** or **Maintain Calculated Fields for Report** shows Convert.
-   Run **Calculated Field Exception Audit** before the integration test. An exception that is only a warning in the report UI still changes the file your vendor receives.

**Business Object Details** shows which fields the object actually has. A column the model invented will not appear in the prompt.

## A consultant’s review before the URL is shared

1.  Copy standard reports. Enable the copy.
2.  Confirm advanced or search, owner username has no `\`, and the report is not temporary.
3.  Set **Enable As Web Service**. Record the namespace. Do not “tidy” it after the first successful call.
4.  Choose one output and save the matching URL (CSV, JSON, Simple XML, or Workday XML / XSD / WSDL).
5.  Run the report as a user who should see the data and as a user who should not. The URL uses that account’s security.
6.  If an outbound EIB will call it, test the EIB in the same non-production tenant. Namespace or column-order drift shows up as a failed transform, not as a report error.
7.  If you used Deployment Agent to list reports, rate the answer. The list is a starting inventory. The report definition is the source of truth.

Facet options, Prism, and Worksheets are separate advanced options. They do not replace the web service flag. Search-report facet XML aliases exist only after **Enable As Web Service** is selected.

## Failure modes

| What breaks | Published cause |
| --- | --- |
| GET fails immediately | Report owner username contains a backslash. |
| Callers fail after a “harmless” edit | Namespace changed and the integration still sends the old one. Two reports can also share a namespace because uniqueness is not enforced. |
| Excel shows the wrong characters | CSV is UTF-8 and the URL is missing `&bom=true`. |
| Excel columns look regrouped or reordered | CSV drops group headings and may reorder columns. |
| Dates look different in Simple XML | Date-only fields lose time and GMT offset. |
| The report vanished from search |  **Exclude Execution Link from Search** is on. People still need the URL and permission. |
| Integration hits a deleted definition | The report was temporary and someone ran the delete task. |
| Standard report mapping breaks after a Workday update | You enabled the delivered report instead of a custom copy. |

## Watch Kiweely Vine turn a report into a web service and an Outbound EIB

![View Background Process in Workday: the IT Worker Provisioning Outbound EIB Kiweely Vine built has completed](https://kiweely.com/guides/ai-workday-custom-reports-raas-for-consultants/media/vine-outbound-eib-f0ae4ace5010.webp)

From the film: the Outbound EIB completes in two seconds.

From a plain request, Kiweely Vine builds a custom report on active workers, enables it as a web service with an organization prompt, makes it the source of an Outbound EIB, launches it in a Workday Development tenant and checks the output file against the tenant’s workers. 21 minutes from the request to the checked output.

[Watch the film (2 min)](https://www.youtube.com/watch?v=pWXwAHrtDc4) · [Start for free](https://kiweely.com/sign-in?intent=signup)

## Frequently asked questions

### Can Deployment Agent create the RaaS endpoint?

The published sample asks it to **show** custom reports in a tenant. Creation and **Enable As Web Service** are still **Edit Custom Report** on the Advanced tab. The agent does not replace that task.

### Is RaaS the same as a public API?

No. Workday limits the external link to users with a valid tenant account and permission to view the report and the data. RSS is the output type the concept topic describes as usable without a Workday login. Treat RSS as a separate decision.

### Which output should a benefits file use?

The concept topic names payroll and benefits providers as integration examples and points REST or SOAP integrations at Workday XML, with Simple XML as the lighter alternative. Match the file your provider already parses. Changing output type changes the URL and the schema.

### Do I need Workday Extend to use RaaS?

Extend applications are one consumer. Integrations and Excel are the others. You can enable a report as a web service without building an Extend app.

## Sources checked

Frontmatter pages, fetched 2026-11-16. The report-discovery sentence is Workday’s published sample.

## Sources checked

-   [Concept: Reports as a Service (RaaS)](https://doc.workday.com/admin-guide/en-us/reporting-and-analytics/custom-reports-and-analytics/reports-as-a-service-raas-/dan1370796320263.html)
-   [Set Up Advanced Options for Custom Reports](https://doc.workday.com/admin-guide/en-us/reporting-and-analytics/custom-reports-and-analytics/set-up-reports/blz1474396724926.html)
-   [Deployment Agent Sample Prompts for Implementation Environments and Customer Central](https://doc.workday.com/admin-guide/en-us/workday-ai/agents/workday-built-agents/deployment-agent-in-implementation-environments-an/reference--deployment-agent-sample-prompts-for-imp.html)
-   [Setup Considerations: Calculated Fields](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/calculated-fields/ova1547251060954.html)

## Related guides

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

-   [### HCM prompt library for Workday implementers using Deployment Agent Workday published CRAFT and a handful of samples, including a Worker management-level calculated field and a tenant report listing. This library tags each HCM prompt as published or as a fill-in that uses only those elements, so you do not treat a pattern as a Workday-certified script.](https://kiweely.com/guides/workday-ai-prompt-library-hcm-implementers)
-   [### EIB spreadsheet mapping when an AI assistant drafts the load Inbound EIBs load spreadsheet rows through a web service. This guide uses Workday’s payroll-input example to show ID type versus ID value, then uses the Deployment Agent SOAP example so a parent-element fault is not treated as a mapping success.](https://kiweely.com/guides/ai-workday-eib-mapping-for-consultants)
-   [### Prove an AI-suggested Workday calculated field before it drives a condition rule Deployment Agent’s documented example suggests Evaluate Expression logic for a Worker field and you build it in Create Calculated Field; Configuration Cloud (partner early access) can make approved changes. This guide shows how to prove the field before a rule or integration uses it.](https://kiweely.com/guides/ai-workday-calculated-fields-condition-rules-proof)
-   [### CRAFT prompts for the Workday Deployment Agent Workday’s Deployment Agent sample-prompts topic, updated 2026-11-06, says accurate answers come from five CRAFT elements. This guide restates that method, shows which elements you can omit, and rewrites the published samples so an administrator can see what each word is doing.](https://kiweely.com/guides/workday-deployment-agent-admin-prompt-patterns)

### More guides on Integrations and APIs

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

-   [Run Workday Studio AUnit Before You Accept AI Edits](https://kiweely.com/guides/workday-studio-aunit-before-ai-edits)
-   [What AI tools can a Workday consultant use to build reports, calculated fields and EIB loads faster?](https://kiweely.com/guides/ai-tools-for-workday-reports-calculated-fields-eib)
-   [Which Workday Integrations May Auto-Remediate](https://kiweely.com/guides/which-workday-integrations-may-auto-remediate)
-   [An Integration Run Book Assistants Can Query](https://kiweely.com/guides/workday-integration-run-book-for-assistants)
-   [When Workday Integrations Should Leave the Tenant](https://kiweely.com/guides/when-workday-integrations-leave-the-tenant)
-   [Workday API Rate Limits When Many Employees Ask Questions in Chat](https://kiweely.com/guides/workday-rate-limits-when-employees-ask-in-chat)
-   [Workday SFTP File Contracts, PGP, and Overnight Failures](https://kiweely.com/guides/workday-sftp-file-contracts-pgp-overnight-failures)
-   [Recover Workday Integration Attributes After a Sandbox Refresh](https://kiweely.com/guides/workday-sandbox-refresh-integration-attributes)

### From the blog on Integrations and APIs

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

-   [The Slow Change Cycle in Workday Studio (and How to Break It)](https://kiweely.com/blog/workday-studio-slow-change-cycle)
-   [Kiweely builds, deploys and runs a Workday Studio integration from one request](https://kiweely.com/blog/workday-studio-integration-built-deployed-and-run)
-   [Why does a Workday EIB load fail, and how do you get a clean load the first time?](https://kiweely.com/blog/why-workday-eib-load-fails)

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