Connect Workday#

Reportworq reaches Workday itself (Financial Management or HCM) through the CData Workday driver. This is a different connector from Workday Adaptive Planning, which is the planning product on the Adaptive Planning API and refreshes OfficeConnect Excel reports; if you want that connector instead, see Connect Workday Adaptive Planning.

The Workday driver's Connection Type property selects which Workday surface it exposes as tables: WQL, Reports (Reports-as-a-Service, or RaaS), REST, or SOAP. This page covers Reports mode, the usual choice for financial and HCM reporting, and the setup step that trips up most first attempts: Custom Report URL must point at a catalog report you build in Workday, not at the data report you actually want.

How it works#

In Reports mode the driver does not read your target report directly. Instead:

1. You build a small catalog report in Workday, an Advanced report over the Custom Report business object, that lists the web-service-enabled custom reports available to the integration user.
2. Custom Report URL on the Reportworq connection points at that catalog report's own web-service URL.
3. At connection time, the CData driver calls the catalog report to discover which reports it lists, and exposes each listed report as its own table.

That is why pointing Custom Report URL at the data report you want (the natural first guess) fails with "The CustomReportURL report does not list any valid RaaS reports." The URL is not the data; it is the catalog that tells the driver where the data reports are.

What you'll need#

• You are a Reportworq administrator. Only administrators can add or configure datasource connections.
• A Workday administrator (or you, with report-building and web-service access in Workday) to build the catalog report and share it with the integration user.
• The Workday Tenant and Base URL for your tenant, and OAuth or Basic credentials for the integration user Reportworq will authenticate as.
• The one or more Workday custom reports you actually want Reportworq to read, already built and, ideally, already enabled as web services individually; the catalog report lists them, it does not create them.

Set it up#

1. Build the catalog report in Workday#

In Workday, create a new Custom Report:

1. Report type: Advanced.
2. Primary business object: Custom Report.
3. Add these four columns, each with an empty Column XML Alias (leave the alias field blank on every one):
   • Report Name
   • Web Service Namespace
   • Report Owner
   • Brief Description
4. On the Filter tab, filter to reports that are actually web-service-enabled: Web Service Namespace is not blank. Optionally add Current User as well, so the report only lists reports the requesting user owns.
5. On the Advanced tab: check Enable As Web Service, and leave Optimized for Performance unchecked; Optimized for Performance suppresses the columns the driver needs to discover reports and breaks the catalog.
6. Share the catalog report with the Reportworq integration user. That user must also be able to run the underlying data source the catalog report is built on, not just view the report definition; a user who can see the catalog but cannot run its data source still gets an empty or failing catalog.

2. Get the catalog report's web-service URL#

1. Run the catalog report, or open it, and choose the related actions ("...") menu on the report.
2. Go to Web Services > View URLs.
3. Copy the Workday XML URL. This is the URL Reportworq needs, not the HTML, PDF, or other format links on the same page.

3. Enable each data report as a web service#

Each report you actually want to read as a table must itself be enabled as a web service (its own Advanced tab, Enable As Web Service checked) and shared with the integration user, the same as the catalog report. The catalog report only lists reports; Workday still enforces access and web-service exposure per report.

4. Add the connection in Reportworq#

1. Sign in to Reportworq as an administrator and go to Settings > Integrations. Datasource connectors live under the DATASOURCES heading.
2. Select Add integration, find Workday in the catalog, and add it. The connection editor opens.
3. Select Enable datasource connection and give the connection a Datasource Name. This name is how parameters and formulas refer to the datasource, so it must be unique across the instance and is awkward to change later.
4. Enter Tenant and Base URL for your Workday tenant.
5. Set Connection Type to Reports.
6. Set Custom Report URL to the catalog report's Workday XML URL from step 2 (the catalog report, not the data report).
7. Choose an Auth Scheme (OAuth or Basic) and enter the integration user's credentials.
8. Select Test connection. On success, each report the catalog lists appears as its own table.
9. Select Save.

Query the data#

Once the connection tests, each report the catalog lists is available as a table in table or SQL mode, exactly as for the other CData connectors, see Query the source in a data model. If a report you expect is missing, confirm it is individually web-service-enabled and shared with the integration user (step 3); the catalog only lists what it can see.

Bring a WQL query in as a table#

Bring the result of a Workday Query Language (WQL) query in as a table you can use in any data model, for example a headcount-by-cost-center query or a list of open journal lines. You do not have to build and web-service-enable a custom report in Workday first: paste the query, and the result becomes a table on the connection that refreshes from Workday on every job run. Reportworq calls this an Import, and the action on a Workday connection is Import WQL report.

The connection's Connection Type must be WQL. Import WQL report is offered only while Connection Type is WQL, which is the driver's default when the property is left empty. On a connection set to Reports, REST, or SOAP, including the Reports mode setup described above, the action does not appear. To use both, add a second Workday connection with Connection Type set to WQL.

Only a system administrator can run an Import. For everyone else the button is shown but disabled.

1. Get a starting query. In Workday, run the Convert Report to WQL task against the report you want; it produces WQL you can paste in and adjust.
2. Open a data model that reads from the WQL-mode Workday connection, and open a view on its Design tab.
3. In the toolbar above the canvas, select Import WQL report.
4. Enter a Table name. It must not match a table the connection already has.
5. Paste the query into WQL query.
6. If the query takes parameters, list them in Parameters as a comma-separated list of name:Type. The types are Instance, Text, Boolean, Time, Date, DateTimeZone, and Numeric.
7. Select Import. When it succeeds, select Close: the new table becomes the view's starting table on the canvas.

You can also run Import WQL report from the connection's own page (Settings > Integrations > the Workday connection), in its Imported objects section, which is also where you regenerate or remove an imported table. For how imported tables behave, and the read-only Tools a Workday connection carries, see Bring reports and saved searches in as tables.

If you later change the connection's Connection Type away from WQL, tables imported this way show as Not available in the current mode and can only be removed.

Behavior and limits#

• What a connection can see is set by the Workday user, not by Reportworq. The connector exposes only the data sources the authenticating Workday user is entitled to. An integration user holding HR security alone returns HR data and no financial data, which looks exactly like a connector that "only does HR." If financial data is missing, widen the integration user's security in Workday rather than changing anything in Reportworq.
• "Workday" and "Workday Adaptive Planning" are two different connectors. Adding the wrong one is the most common mistake here; see Connect Workday Adaptive Planning.
• WQL, REST, and SOAP are the other Connection Type choices. WQL suits live querying of Workday data sources without building a catalog report. REST and SOAP are lower-level; SOAP additionally needs Service, WSDL Source, and WSDL Version, and is the fiddliest of the four. This page covers Reports mode setup, plus importing a WQL query as a table on a WQL connection (see Bring a WQL query in as a table).

Troubleshooting#

Related#

• Connector catalog for the full connector list and per-connector traps.
• Connect CData sources for the shared CData setup flow.
• Connect Workday Adaptive Planning for the planning product, a separate connector.
• Connect a data source for the general add, test, and manage flow.