---
title: "Fix Graph API DataSourceFilter & processingWorker Errors"
description: "Resolve Graph API DataSourceFilter is inaccessible errors and blank processingWorker contact fields when proxying as a non-admin employee in Workday Extend."
url: https://kiweely.com/guides/workday-graphql-datasourcefilter-inaccessible-processingworker-proxy
---

# Fixing Graph API DataSourceFilter Is Inaccessible Errors and Blank processingWorker Fields When Proxying

Workday Graph API queries fail with DataSourceFilter is inaccessible when the caller lacks View access to the domain securing the filter, and silently return blank fields on processingWorker when Employee As Self lacks contact domain permissions.

-   **Checked** against Workday on November 6
-   Applies to **Workday Extend**
-   4 min read
-   Published November 6
-   By Kiweely

## Problem 1: `"DataSourceFilter: <filterName> is inaccessible"` in Graph API

When you generate a GraphQL query in **Graph API Explorer** and run it against an Implementation (`IMPL`) or Sandbox tenant, the query can fail even after you have granted the user or Integration System Security Group (`ISSG`) access to the **Graph API Descriptor** and **Workday Graph API Applications** domains:

json

```
{
  "errors": [
    {
      "message": "DataSourceFilter: automatedExpensesReportLineFilter is inaccessible"
    }
  ]
}
```

Granting **Graph API Descriptor** and **Workday Graph API Applications** only unlocks access to the GraphQL gateway itself. Every GraphQL query in Workday requires a `dataSource` argument (such as `automatedExpensesReportLineFilter` on `ExpenseReportLine_DataSources` or `processingWorker` on `Worker_DataSources`), and each data source filter is individually secured by the functional reporting domain of the underlying Workday module.

### Fix: Audit the Data Source Filter’s security domain and Activate Pending Security Policy Changes

To find and grant the exact domain required by the inaccessible data source filter:

1.  In your Workday tenant, run the **View Security for Securable Item** task.
2.  Search for the exact data source or data source filter name reported in the error message (for example, **Automated Expense Report Line Filter** or **Expense Report Lines for Worker**).
3.  Inspect the **Domain Security Policies** and **Business Process Security Policies** securing that item. Note that a data source filter is often secured by a more specific domain than the parent business object (for example, an expense line filter secured by **Self-Service: Expense Reports** or **Expense Report Lines for Worker** rather than general worker reporting).
4.  Add your target security group (`ISSG` for `isuAuth` or `Employee As Self` / role group for `sso`) to the **Report/Task Permissions (View)** list on that domain.
5.  Run **Activate Pending Security Policy Changes** so the updated domain policy takes effect immediately.

## Problem 2: `processingWorker` returns blank `email_PrimaryWork` and manager emails for non-admin proxy users

A common pattern on Workday Extend pages is calling a `workday-graph` endpoint on page load with `dataSource: { processingWorker: {} }` to fetch the logged-in user’s profile, primary work email, cost center, and manager’s work email:

graphql

```
query {
  me: worker(dataSource: { processingWorker: {} }) {
    data {
      workdayID {
        id
      }
      descriptor
      businessTitle
      preferredName {
        firstName
        lastName
      }
      email_PrimaryWork
      employeeID
      workersManagers {
        data {
          workdayID {
            id
          }
          descriptor
          email_PrimaryWork
        }
      }
      primaryJob {
        costCenter {
          data {
            code
            descriptor
          }
        }
        descriptor
      }
      supervisoryOrganization_PrimaryPosition {
        descriptor
      }
    }
  }
}
```

When an administrator runs the Extend app, every field in `me.data[0]` populates as expected. However, when you **Start Proxy** as a standard non-admin employee, `workdayID`, `descriptor`, and `preferredName` return data, while `email_PrimaryWork` and `workersManagers.data[0].email_PrimaryWork` come back blank (`null` or `""`) with zero errors in the GraphQL response.

### Root cause: Silent field-level security redaction in GraphQL

When a GraphQL query executes under `"authType": "sso"`, Workday evaluates field-level reporting security for each selected field against the logged-in persona’s security groups (typically **Employee As Self** for `me` and unconstrained/public worker data for `workersManagers`).

Unlike an inaccessible `DataSourceFilter`—which rejects the entire query—when a user lacks domain **View** access to an individual field or Related Business Object (`RBO`) field inside a selection set, Workday GraphQL **silently redacts that field to `null`/blank** rather than failing the query.

Specifically:

-   Reading the user’s own `email_PrimaryWork` requires **Employee As Self** to have **View** permission on the domain securing work contact email (**Person Data: Work Contact Information** / **Self-Service: Work Contact Information**).
-   Reading `workersManagers { data { email_PrimaryWork } }` crosses from the logged-in worker (`Self`) to a different worker record (the manager). **Employee As Self** only grants self-access; it cannot read another worker’s `email_PrimaryWork` unless an unconstrained group (such as **All Employees** or **All Users**) has **View** access to public work email contact information, or the query runs under an Integration System User (`isuAuth`).

### Fix options

Depending on your security architecture, use one of two fixes:

1.  **Switch the `meGraph` lookup to `"authType": "isuAuth"` (when manager contact info is required regardless of employee directory visibility):** Instead of using `processingWorker` (which resolves to the ISU itself when called under `isuAuth`), pass the logged-in worker’s `workdayID` (from `workers/me`) as a `$workerId` filter to a `worker` GraphQL query or `WQL` query authorized via `"authType": "isuAuth"`, where the app’s Simplified ISU has `View` access to **Person Data: Work Contact Information**.
2.  **Grant domain `View` access for `sso` queries:** Run **View Security for Securable Item** on `email_PrimaryWork` (**Primary Work Email**), verify which domain secures the report field in your tenant, and add **Employee As Self** (for self) and **All Employees** (if employees are permitted to view manager work emails) to the **View** permission list, followed by **Activate Pending Security Policy Changes**.

## How to verify the fix in your tenant

1.  Run **Start Proxy** as a standard employee who holds only **Employee As Self** (no administrator or HR Partner roles).
2.  Open your Extend page and inspect the network/debug response of the `me_graph` endpoint.
3.  Confirm that `email_PrimaryWork` and `workersManagers.data[0].email_PrimaryWork` return the populated email strings and that no `DataSourceFilter is inaccessible` errors appear in the response.

## Sources checked

-   [Workday Graph API Authentication and Security](https://developer.workday.com/documentation/GUID-8b37afd9-22d7-42ba-b150-e979466f1525-enHYPHENus)
-   [Graph API Queries](https://developer.workday.com/documentation/qxq1671067079349)
-   [Generate Queries on Graph API Explorer](https://developer.workday.com/documentation/uip1679531855079)
-   [Run Graph API Queries on a Page](https://developer.workday.com/documentation/ydz1559023281482)
-   [Define Endpoint Authentication in the PMD](https://developer.workday.com/documentation/yea1530546235609)

## Related guides

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

-   [### Handling Silent GraphQL Errors in PMD and Orchestrate When HTTP Status Returns 200 OK Workday Graph API endpoints return HTTP 200 OK even when a query or mutation fails with an S21 or validation error inside the JSON errors array. Inspect $.errors explicitly in Orchestrate and verify that your .amd base URL version matches Graph API Explorer.](https://kiweely.com/guides/workday-graphql-http-200-silent-mutation-errors)
-   [### Clearing Single-Instance Relationships to Null and Binding createdBy with graph:createId() in Graph API Workday Graph API mutations require nested IdentifierInput objects for single-instance relationships like createdBy—which you can generate cleanly in PMD with graph:createId(id). To clear an existing single-instance relationship back to null, use the Model Business Object REST PUT or PATCH API.](https://kiweely.com/guides/workday-graphql-clear-single-instance-null-graph-createid)
-   [### Why Attachment Model Components and contentType Are Missing from the GraphQL Schema After Migrating to IMPL After promoting a Workday Extend app with an Attachment Business Object to an Implementation or Sandbox tenant, GraphQL queries can fail with Unknown type \_DataSources or missing contentType fields. Refresh the model cache, verify ISU domain security, and check tenant Graph schema availability.](https://kiweely.com/guides/workday-graphql-attachment-schema-contenttype-missing-impl)
-   [### Filtering WQL Queries by Organization Hierarchy and workersByRole Without Throwing Security Errors To return workers in an HR Partner’s assigned organizations and subordinate hierarchies, use workersForHCMReporting with dataSourceFilter = workersByRole. Guard the endpoint with an exclude check so users without the constrained role do not trigger a hard WQL error.](https://kiweely.com/guides/wql-organization-hierarchy-filter-workersbyrole)

### More guides on Extend apps and pages

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

-   [Splitting New and Existing PMD Grid Rows in onSend for Bulk POST and PATCH Without Duplicating Records](https://kiweely.com/guides/workday-extend-pmd-split-new-modified-grid-rows-bulk-post-patch)
-   [Fixing radioGroup Options Disappearing When selectedValues Is Empty and Disabling Specific Options in Workday Extend PMD](https://kiweely.com/guides/workday-extend-pmd-radiogroup-options-disappear-disable-specific-items)
-   [Why a RaaS Endpoint Returns HTTP 200 with data as null in PMD and How to Surface SOAP Fault Messages](https://kiweely.com/guides/workday-extend-pmd-raas-report-entry-null-soap-fault-http-200)
-   [Why PATCH from an SSO PMD Page Fails with unrecognized field While the Same Payload Succeeds in Postman](https://kiweely.com/guides/workday-extend-pmd-patch-unrecognised-field-sso-vs-postman)
-   [Deleting Selected Grid Rows and Fixing Parallel Multi-Instance Arrays Collapsing on Edit Pages in Workday Extend PMD](https://kiweely.com/guides/workday-extend-pmd-grid-delete-selected-rows-parallel-arrays-collapse)
-   [Displaying dynamicColumns in a Workday Extend PMD Grid and Flattening Nested Arrays into Rows](https://kiweely.com/guides/workday-extend-pmd-dynamic-grid-columns-flattening-arrays)
-   [Conditional Page Routing on Load, multiStepLayout vs. tabBar Navigation, and flowVariables Payload Limits in Workday Extend PMD](https://kiweely.com/guides/workday-extend-pmd-conditional-page-routing-tabbar-flowvariables-limits)
-   [Clearing Grid Cell Validation Errors on onChange and Blocking Page Save on pageActionButton Failure in Workday Extend PMD](https://kiweely.com/guides/workday-extend-pmd-clear-grid-cell-error-pageactionbutton-block-save)

### From the blog on Extend apps and pages

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

-   [Claude Code vs Codex for Workday Extend: What Each Can Reach Today](https://kiweely.com/blog/claude-code-vs-codex-for-workday-extend)
-   [Workday Extend vs. External Pass-Through Screens: Which Architecture Fits Your Workflow?](https://kiweely.com/blog/workday-extend-vs-external-pass-through-apps-decision-guide)
-   [How to Put Custom Employee Screens in Front of Workday Without a Workday Extend License](https://kiweely.com/blog/custom-employee-ui-for-workday-without-workday-extend)

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