---
title: "Fix Workday EIB Duplicate Key and Reference IDs — Kiweely"
description: "Resolve Workday EIB duplicate Spreadsheet Key issues and invalid Reference ID lookups using View Reference IDs, Integration IDs, Validate Only, and error files."
url: https://kiweely.com/guides/workday-eib-duplicate-key-reference-id-errors
---

# How to Fix The Load Contains a Duplicate Key and Invalid Reference ID Errors in Workday EIB

Inbound Workday EIB failures that mention a duplicate key usually mean Spreadsheet Key or Reference ID uniqueness is wrong in the workbook. Invalid Reference ID failures mean a typed ID does not match a live tenant object. Fix keys, verify IDs, then Validate Only before reloading.

-   **Checked** against Workday on November 13
-   Applies to **Workday Integrations**
-   5 min read
-   Published November 13
-   By Kiweely

When an inbound Workday **Enterprise Interface Builder (EIB)** rejects rows for a duplicate key or an invalid Reference ID, the spreadsheet is naming the wrong transaction identity or pointing at an object ID that does not exist in that tenant. Fix uniqueness of **Spreadsheet Key** (and any Reference ID used as a natural key), verify every lookup ID with **View Reference IDs** or **Integration IDs > View IDs**, then relaunch with **Validate Only** before a live load.

To check what your own messages say, paste them into the [EIB error explainer](https://kiweely.com/tools/workday-eib-errors): it names the value and ID type back and gives the fix from Workday’s documentation.

Exact error phrasing can vary by web service operation and Workday release. Treat the messages practitioners summarize as “duplicate key” and “invalid Reference ID” as symptoms of the two failure families below, and always read the wording on your integration event via Workday’s **View Error Messages for an EIB** guidance and the attached error files.

## Failure Family 1: Duplicate Key / Spreadsheet Key Collisions

Inbound EIB templates turn spreadsheet rows into Workday Web Services requests. The **Spreadsheet Key** column tells Workday which rows belong to the same parent transaction.

Workday’s data-entry topics are consistent across products:

-   Advanced Lookup Table EIBs: all rows for one lookup table share one Spreadsheet Key; a new table needs a new Spreadsheet Key.
-   Career Path EIBs: specify a unique Spreadsheet Key per career path; repeat that value on every step row for that path.
-   Period Schedule and Payroll Input EIBs: one Spreadsheet Key groups the parent record plus its child Row ID lines (usages, periods, related calculations).

| Spreadsheet Pattern | Result | Fix |
| --- | --- | --- |
| Same Spreadsheet Key on two unrelated parents | Workday treats them as one malformed transaction or rejects the load for key conflict | Assign a new Spreadsheet Key per parent transaction |
| Two different Spreadsheet Keys on child lines of one journal/worker | Parent and children split into separate requests | Copy the parent Spreadsheet Key onto every child Row ID line |
| Identical full rows pasted twice with the same key and IDs | Duplicate natural keys inside one load | Deduplicate before upload; do not “retry” by stacking copies |

Fails

```
# Two workers accidentally share Spreadsheet Key 1
Spreadsheet Key | Employee ID | Earning            | Amount
1               | 21001       | Transportation     | 50
1               | 21002       | Transportation     | 50
```

Works

```
Spreadsheet Key | Employee ID | Earning            | Amount
1               | 21001       | Transportation     | 50
2               | 21002       | Transportation     | 50
```

For multi-instance custom objects, Workday also warns that duplicate values in the custom field used as Reference ID cause later EIB rows to overwrite earlier ones. Unique keys are not optional there either.

## Failure Family 2: Invalid or Misused Reference IDs

Reference ID errors mean the workbook’s ID cell does not resolve to an instance in the target tenant (wrong ID, wrong ID type, wrong environment after a refresh, inactive object, or a display name pasted where an ID is required).

Verified lookup methods from Workday admin topics:

1.  Run **View Reference IDs** and select the business object named by the template column (Job Profile, Frequency, Pre-Defined Career Path, and so on).
2.  On a known good instance, open related actions **Integration IDs > View IDs** and copy the Type and ID values.
3.  Prefer regenerating the template with **Generate Spreadsheet with Data** when you are updating existing records so Workday pre-fills current IDs.

Fails

```
# Display name pasted into an ID column
Career Step Job Profile | HR Business Partner
# Template expects the Job Profile reference ID from View Reference IDs
```

Works

```
Career Step Job Profile | JOB_PROFILE-6-217
# Exact ID from View Reference IDs for Job Profile in this tenant
```

A related, equally common mistake: leaving an update ID blank when you meant to modify an existing record. For **Import Payroll Input**, Workday documents that a blank Payroll Input ID generates a new reference ID and can create duplicate inputs if you rerun the sheet. The same create-vs-update pattern appears on period schedules and other Put/Import templates: blank ID creates; populated ID updates.

## Diagnosis Order That Avoids Partial Reloads

1.  Open the integration event and follow **View Error Messages for an EIB**. Download `FailureReport.html`, `ErrorsAndWarningsSpreadsheet.xml`, and `OriginalDataWithErrors.xml` while they are still retained (Workday keeps those inbound troubleshooting files for **60 days**).
2.  Separate key collisions from Reference ID lookup failures in the error sheet. Fix Spreadsheet Key groups first; ID typos second.
3.  Confirm you are loading the tenant you think you are. Sandbox refresh changes which Reference IDs exist even when the workbook looks unchanged.
4.  Relaunch with **Validate Only** (or the equivalent validate option on **Launch / Schedule Integration**) until the event completes without those errors.
5.  Only then run the live load, and only for Spreadsheet Key groups that still need creating or updating.

Also respect inbound size and runtime limits when large error volumes appear: browser uploads cap at **30 MB**, external transports allow larger XLSX/XML sizes, and inbound web service loads have a **5-hour** runtime ceiling with **2 hours** for error-file generation. See the broader [EIB load errors](https://kiweely.com/guides/workday-eib-load-errors) and [EIB results and error toolbar](https://kiweely.com/guides/workday-eib-results-error-toolbar) guides for event navigation.

Validate Only does not replace ID verification

Validate Only catches many schema and reference problems early, but it cannot invent missing tenant data. If View Reference IDs does not return the ID you typed, fix the workbook or create the missing foundation data before another launch.

## Prevention Checklist for the Next Template

-   Generate the spreadsheet from the current template model; do not reuse an old workbook from another tenant.
-   Keep one Spreadsheet Key per parent transaction; increment Row ID only inside that key.
-   Populate existing object IDs when updating; leave create-only ID cells blank only when Workday is supposed to assign a new ID.
-   Never paste worker names, org names, or plan labels into Reference ID columns.
-   After any failed live run, reload only the failed Spreadsheet Key set. Inbound EIBs commit successful transactions independently, so a blind full-file retry can duplicate already-loaded rows.

If you want a messy inbound workbook checked for Spreadsheet Key collisions and Reference ID mismatches against a connected tenant before launch, [Kiweely Vine](https://kiweely.com/vine) can inspect the sheet and live IDs, then propose a cleaned load file for your approval. 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

### What is Spreadsheet Key supposed to identify in a Workday EIB workbook?

Spreadsheet Key identifies one parent web service transaction in the spreadsheet. Every child row that belongs to that same transaction repeats the same Spreadsheet Key. A different parent transaction needs a different Spreadsheet Key.

### Why did rerunning the same EIB create duplicate payroll inputs?

For Import Payroll Input style templates, leaving Payroll Input ID blank causes Workday to generate a new reference ID on import. Running that same sheet again creates another input instead of updating the first one. Populate the existing Payroll Input ID when you intend to update.

### Where do I look up the Reference ID value an EIB column expects?

Use View Reference IDs for the business object named in the template column, or open Integration IDs then View IDs from the related actions menu on a sample instance. Copy the ID type and ID value exactly into the spreadsheet.

### How long does Workday keep EIB error troubleshooting files?

Workday retains inbound troubleshooting files such as ErrorsAndWarningsSpreadsheet.xml, FailureReport.html, and OriginalDataWithErrors.xml for 60 days. Use those attachments from the integration event before reloading only the failed Spreadsheet Key groups.

## Sources checked

-   [Concept: EIB Spreadsheet Data Entry Guidelines](https://doc.workday.com/admin-guide/en-us/integrations/enterprise-interface-builder-eib-/inbound-eibs/dan1370796370630.html)
-   [View Error Messages for an EIB](https://doc.workday.com/admin-guide/en-us/integrations/enterprise-interface-builder-eib-/eib-general-errors-and-guidelines/dan1370797979718.html)
-   [Concept: Data Entry in Payroll Input EIB Spreadsheets](https://doc.workday.com/admin-guide/en-us/payroll/payroll-input/zzm1518620193483.html)
-   [Concept: Data Entry in Advanced Lookup Table EIB Spreadsheets](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/calculations/icf1629235546236.html)
-   [Reference: Integrations, EIB, and Web Service Limits](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/it-administrator-resources/limitations-and-availability/dan1370797408285.html)

## Related guides

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

-   [### How to Blank Out Text Fields and Nullify Reference Values on Workday Extend Business Objects via Inbound EIB Using {empty} Leaving a spreadsheet cell blank or entering “” or null in an Inbound EIB does not clear existing field values on a Workday Extend Business Object. Learn how to use the {empty} tag, avoid the leading/trailing whitespace trap in Excel, and remove specific multi-instance values.](https://kiweely.com/guides/workday-extend-eib-clear-text-nullify-fields-empty-tag)
-   [### Generating and Validating a Workday EIB Spreadsheet Template Without Corrupting Headers Generate inbound Workday EIB templates via Template Model > Generate Spreadsheet Template and keep the hidden XML metadata in Rows 1-5 intact. Learn how Spreadsheet Key, Row ID, Separate Type Column, and Paste Values prevent schema corruption and load failures.](https://kiweely.com/guides/workday-eib-generate-spreadsheet-template-errors)
-   [### Is there a Workday EIB error toolbar? Where load results and error files are Workday’s public docs describe no EIB ‘error toolbar’. An inbound EIB’s results sit on its integration event: View Background Process, the Messages tab and Execution Summary, and the error files Workday attaches. Includes reloading only the failed rows.](https://kiweely.com/guides/workday-eib-results-error-toolbar)
-   [### Workday EIB vs Core Connector vs Cloud Connect vs Studio: which to use Use an end-to-end Cloud Connect connector if one exists for the vendor, a Core Connector for a delivered template with change detection, EIB for simple guided loads, and Studio for multiple web service calls or complex error handling.](https://kiweely.com/guides/workday-studio-vs-eib-vs-cloud-connect)
-   [### Why did my Workday EIB load fail? Fix Invalid ID Value and field restriction errors Open the integration event on View Background Process. For Completed With Errors, select Number of Errors to read each row’s message. Invalid ID Value is a wrong Reference ID; ‘does not meet the restrictions’ names the field, and in Workday’s example the launching user lacked security for it.](https://kiweely.com/guides/workday-eib-load-errors)

### More guides on Integrations and APIs

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

-   [How to Troubleshoot Workday Cloud Connect for Benefits (CCB) and Missing Dependents on 834 Feeds](https://kiweely.com/guides/workday-cloud-connect-for-benefits-834-errors)
-   [Why Workday Scheduled Reports and Integrations Shifted Dates After Local Time Zone Processing](https://kiweely.com/guides/workday-local-time-zone-processing-report-integration-impacts)
-   [Workday Mass Job Change Tables vs. Change Job EIB: Limits, Security, and When to Use Each](https://kiweely.com/guides/workday-mass-job-change-vs-eib)
-   [Workday Data Cloud vs. EIB, RaaS, and Prism: Which Data Path Should You Use?](https://kiweely.com/guides/workday-data-cloud-vs-eib-raas-prism)
-   [How to change job profile and compensation in one Change Job SOAP request](https://kiweely.com/guides/workday-change-job-soap-profile-compensation)
-   [Why the Workday REST /workers endpoint leaves out terminated workers](https://kiweely.com/guides/workday-rest-api-workers-terminated)
-   [How to get the instance ID back after a POST to the Workday REST API](https://kiweely.com/guides/workday-rest-api-instance-id-after-post)
-   [How the Workday REST API batch protocol works](https://kiweely.com/guides/workday-rest-api-batch-protocol)

### From the blog on Integrations and APIs

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

-   [Why Most Workday Studio Integrations Ship Without Tests](https://kiweely.com/blog/workday-studio-integrations-without-tests)
-   [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)

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