- Introduction
-
Getting Started
- Creating an Account in Hevo
- Subscribing to Hevo via AWS Marketplace
- Subscribing to Hevo via Snowflake Marketplace
- Connection Options
- Familiarizing with the UI
- Creating your First Pipeline
- Data Loss Prevention and Recovery
- Upgrading Pipeline from Standard to Edge
-
Data Ingestion
- Types of Data Synchronization
- Ingestion Modes and Query Modes for Database Sources
- Ingestion and Loading Frequency
- Data Ingestion Statuses
- Deferred Data Ingestion
- Handling of Primary Keys
- Handling of Updates
- Handling of Deletes
- Hevo-generated Metadata
- Best Practices to Avoid Reaching Source API Rate Limits
-
Edge
- Data Ingestion
- Core Concepts
-
Pipelines
- Familiarizing with the Pipelines UI
- Creating an Edge Pipeline
- Working with Edge Pipelines
- Pipeline Job History
- Pipeline Overview
- Needs Attention
- Object and Schema Management
- Activity Log
-
Sources
- Connect AI
- PostgreSQL
- Oracle
- MySQL
- SQL Server
- CockroachDB
- MongoDB
- Troubleshooting Database Sources
- Salesforce Bulk API V2
- Ordergroove
- BambooHR
- Stripe
- NetSuite SuiteAnalytics
- Shopify
- Slack
- ClickUp
- Monday.com
- Pipedrive
- Workable
- Fathom
- HubSpot
- Salesforce Marketing Cloud
- Google Analytics 4
- Google Ads
- Facebook Ads
- Microsoft Ads
- LinkedIn Ads
- Xero
- Instagram Business
- Amazon Selling Partner
- TikTok Ads
- StackAdapt
- Amazon Ads
- Pinterest Organic
- Zendesk Support
- Snapchat Ads
- TikTok Organic
- Google Search Console
- Klaviyo v2
- Braintree Payments
- Facebook Pages
- Tempo
- PayPal
- Auth0
- Pinterest Ads
- Apple Search Ads
- Permit.io
- Amplitude Analytics
- Customer.io
- Paddle
- Jira Cloud
- GitHub
- WorkOS
- ActiveCampaign
- Campaign Monitor
- Metaplane
- Recharge
- sevdesk
- Statuspage
- Teamwork.com
- Workday RaaS
- Yotpo
- Naming Conventions for Source Data Entities
- Destinations
- Transformations
- Alerts
- Activate
- Custom Connectors
-
Releases
- Edge Release Notes - October 2026
- Edge Release Notes - September 2026
- Edge Release Notes - August 2026
- Edge Release Notes - July 2026
- Edge Release Notes - June 2026
- Edge Release Notes - May 2026
- Edge Release Notes - April 2026
- Edge Release Notes - March 2026
- Edge Release Notes - February 2026
- Edge Release Notes - January 2026
- Edge Release Notes - December 2025
- Edge Release Notes - November 2025
- Edge Release Notes - October 2025
- Edge Release Notes - September 2025
- Edge Release Notes - August 2025
- Edge Release Notes - July 2025
- Edge Release Notes - November 2024
-
Data Loading
- Loading Data in a Database Destination
- Loading Data to a Data Warehouse
- Optimizing Data Loading for a Destination Warehouse
- Deduplicating Data in a Data Warehouse Destination
- Manually Triggering the Loading of Events
- Scheduling Data Load for a Destination
- Loading Events in Batches
- Data Loading Statuses
- Data Spike Alerts
- Name Sanitization
- Table and Column Name Compression
- Parsing Nested JSON Fields in Events
-
Pipelines
- Data Flow in a Pipeline
- Familiarizing with the Pipelines UI
- Working with Pipelines
- Managing Objects in Pipelines
- Pipeline Jobs
-
Transformations
-
Python Code-Based Transformations
- Supported Python Modules and Functions
-
Transformation Methods in the Event Class
- Create an Event
- Retrieve the Event Name
- Rename an Event
- Retrieve the Properties of an Event
- Modify the Properties for an Event
- Fetch the Primary Keys of an Event
- Modify the Primary Keys of an Event
- Fetch the Data Type of a Field
- Check if the Field is a String
- Check if the Field is a Number
- Check if the Field is Boolean
- Check if the Field is a Date
- Check if the Field is a Time Value
- Check if the Field is a Timestamp
-
TimeUtils
- Convert Date String to Required Format
- Convert Date to Required Format
- Convert Datetime String to Required Format
- Convert Epoch Time to a Date
- Convert Epoch Time to a Datetime
- Convert Epoch to Required Format
- Convert Epoch to a Time
- Get Time Difference
- Parse Date String to Date
- Parse Date String to Datetime Format
- Parse Date String to Time
- Utils
- Examples of Python Code-based Transformations
-
Drag and Drop Transformations
- Special Keywords
-
Transformation Blocks and Properties
- Add a Field
- Change Datetime Field Values
- Change Field Values
- Drop Events
- Drop Fields
- Find & Replace
- Flatten JSON
- Format Date to String
- Format Number to String
- Hash Fields
- If-Else
- Mask Fields
- Modify Text Casing
- Parse Date from String
- Parse JSON from String
- Parse Number from String
- Rename Events
- Rename Fields
- Round-off Decimal Fields
- Split Fields
- Examples of Drag and Drop Transformations
- Effect of Transformations on the Destination Table Structure
- Transformation Reference
- Transformation FAQs
-
Python Code-Based Transformations
-
Schema Mapper
- Using Schema Mapper
- Mapping Statuses
- Auto Mapping Event Types
- Manually Mapping Event Types
- Modifying Schema Mapping for Event Types
- Schema Mapper Actions
- Fixing Unmapped Fields
- Resolving Incompatible Schema Mappings
- Resizing String Columns in the Destination
- Changing the Data Type of a Destination Table Column
- Schema Mapper Compatibility Table
- Limits on the Number of Destination Columns
- File Log
- Troubleshooting Failed Events in a Pipeline
- Mismatch in Events Count in Source and Destination
- Audit Tables
- Activity Log
-
Pipeline FAQs
- Can multiple Sources connect to one Destination?
- What happens if I re-create a deleted Pipeline?
- Why is there a delay in my Pipeline?
- Can I change the Destination post-Pipeline creation?
- Why is my billable Events high with Delta Timestamp mode?
- Can I drop multiple Destination tables in a Pipeline at once?
- How does Run Now affect scheduled ingestion frequency?
- Will pausing some objects increase the ingestion speed?
- Can I see the historical load progress?
- Why is my Historical Load Progress still at 0%?
- Why is historical data not getting ingested?
- How do I set a field as a primary key?
- How do I ensure that records are loaded only once?
- Why can't I see my Pipelines after logging in?
- Events Usage
-
Sources
- Free Sources
-
Databases and File Systems
- Data Warehouses
-
Databases
- Connecting to a Local Database
- Amazon DocumentDB
- Amazon DynamoDB
- Elasticsearch
-
MongoDB
- Generic MongoDB
- MongoDB Atlas
- Support for Multiple Data Types for the _id Field
- Example - Merge Collections Feature
-
Troubleshooting MongoDB
-
Errors During Pipeline Creation
- Error 1001 - Incorrect credentials
- Error 1005 - Connection timeout
- Error 1006 - Invalid database hostname
- Error 1007 - SSH connection failed
- Error 1008 - Database unreachable
- Error 1011 - Insufficient access
- Error 1028 - Primary/Master host needed for OpLog
- Error 1029 - Version not supported for Change Streams
- SSL 1009 - SSL Connection Failure
- Troubleshooting MongoDB Change Streams Connection
- Troubleshooting MongoDB OpLog Connection
-
Errors During Pipeline Creation
- SQL Server
-
MySQL
- Amazon Aurora MySQL
- Amazon RDS MySQL
- Azure MySQL
- Generic MySQL
- Google Cloud MySQL
- MariaDB MySQL
-
Troubleshooting MySQL
-
Errors During Pipeline Creation
- Error 1003 - Connection to host failed
- Error 1006 - Connection to host failed
- Error 1007 - SSH connection failed
- Error 1011 - Access denied
- Error 1012 - Replication access denied
- Error 1017 - Connection to host failed
- Error 1026 - Failed to connect to database
- Error 1027 - Unsupported BinLog format
- Failed to determine binlog filename/position
- Schema 'xyz' is not tracked via bin logs
- Errors Post-Pipeline Creation
-
Errors During Pipeline Creation
- MySQL FAQs
- Oracle
-
PostgreSQL
- Amazon Aurora PostgreSQL
- Amazon RDS PostgreSQL
- Azure PostgreSQL
- Generic PostgreSQL
- Google Cloud PostgreSQL
- Heroku PostgreSQL
- Upgrading Pipelines with PostgreSQL Sources to Use the pgoutput Plugin
-
Troubleshooting PostgreSQL
-
Errors during Pipeline creation
- Error 1003 - Authentication failure
- Error 1006 - Connection settings errors
- Error 1011 - Access role issue for logical replication
- Error 1012 - Access role issue for logical replication
- Error 1014 - Database does not exist
- Error 1017 - Connection settings errors
- Error 1023 - No pg_hba.conf entry
- Error 1024 - Number of requested standby connections
- Errors Post-Pipeline Creation
-
Errors during Pipeline creation
-
PostgreSQL FAQs
- Can I track updates to existing records in PostgreSQL?
- How can I migrate a Pipeline created with one PostgreSQL Source variant to another variant?
- How can I prevent data loss when migrating or upgrading my PostgreSQL database?
- Why do FLOAT4 and FLOAT8 values in PostgreSQL show additional decimal places when loaded to BigQuery?
- Why is data not being ingested from PostgreSQL Source objects?
- Troubleshooting Database Sources
- Database Source FAQs
- File Storage
- Engineering Analytics
- Finance & Accounting Analytics
-
Marketing Analytics
- ActiveCampaign
- AdRoll
- Amazon Ads
- Apple Search Ads
- AppsFlyer
- CleverTap
- Criteo
- Drip
- Facebook Ads
- Facebook Page Insights
- Firebase Analytics
- Freshsales
- Google Ads
- Google Analytics 4
- Google Analytics 360
- Google Play Console
- Google Search Console
- HubSpot
- Instagram Business
- Klaviyo v2
- Lemlist
- LinkedIn Ads
- Mailchimp
- Mailshake
- Marketo
- Microsoft Ads
- Onfleet
- Outbrain
- Pardot
- Pinterest Ads
- Pipedrive
- Recharge
- Segment
- SendGrid Webhook
- SendGrid
- Salesforce Marketing Cloud
- Snapchat Ads
- SurveyMonkey
- Taboola
- TikTok Ads
- Twitter Ads
- Typeform
- YouTube Analytics
- Product Analytics
- Sales & Support Analytics
- Source FAQs
-
Destinations
- Familiarizing with the Destinations UI
- Cloud Storage-Based
- Databases
-
Data Warehouses
- Amazon Redshift
- Amazon Redshift Serverless
- Azure Synapse Analytics
- Databricks
-
Google BigQuery
- Clustering in BigQuery
- Partitioning in BigQuery
- Structure of Data in the Google BigQuery Data Warehouse
- Loading Data to a Google BigQuery Data Warehouse
- Near Real-time Data Loading using Streaming
- Modifying BigQuery Destinations to Use Service Account Authentication
- Troubleshooting Google BigQuery
- Google BigQuery FAQs
- Hevo Managed Google BigQuery
- Snowflake
- Troubleshooting Data Warehouse Destinations
-
Destination FAQs
- Can I change the primary key in my Destination table?
- Can I change the Destination table name after creating the Pipeline?
- How can I change or delete the Destination table prefix?
- Why does my Destination have deleted Source records?
- How do I filter deleted Events from the Destination?
- Does a data load regenerate deleted Hevo metadata columns?
- How do I filter out specific fields before loading data?
- Transform
- Alerts
- Account Management
- Activate
- Glossary
-
Releases- 2026 Releases
-
2025 Releases
- Release 2.44 (Dec 01, 2025-Jan 12, 2026)
- Release 2.43 (Nov 03-Dec 01, 2025)
- Release 2.42 (Oct 06-Nov 03, 2025)
- Release 2.41 (Sep 08-Oct 06, 2025)
- Release 2.40 (Aug 11-Sep 08, 2025)
- Release 2.39 (Jul 07-Aug 11, 2025)
- Release 2.38 (Jun 09-Jul 07, 2025)
- Release 2.37 (May 12-Jun 09, 2025)
- Release 2.36 (Apr 14-May 12, 2025)
- Release 2.35 (Mar 17-Apr 14, 2025)
- Release 2.34 (Feb 17-Mar 17, 2025)
- Release 2.33 (Jan 20-Feb 17, 2025)
-
2024 Releases
- Release 2.32 (Dec 16 2024-Jan 20, 2025)
- Release 2.31 (Nov 18-Dec 16, 2024)
- Release 2.30 (Oct 21-Nov 18, 2024)
- Release 2.29 (Sep 30-Oct 22, 2024)
- Release 2.28 (Sep 02-30, 2024)
- Release 2.27 (Aug 05-Sep 02, 2024)
- Release 2.26 (Jul 08-Aug 05, 2024)
- Release 2.25 (Jun 10-Jul 08, 2024)
- Release 2.24 (May 06-Jun 10, 2024)
- Release 2.23 (Apr 08-May 06, 2024)
- Release 2.22 (Mar 11-Apr 08, 2024)
- Release 2.21 (Feb 12-Mar 11, 2024)
- Release 2.20 (Jan 15-Feb 12, 2024)
-
2023 Releases
- Release 2.19 (Dec 04, 2023-Jan 15, 2024)
- Release Version 2.18
- Release Version 2.17
- Release Version 2.16 (with breaking changes)
- Release Version 2.15 (with breaking changes)
- Release Version 2.14
- Release Version 2.13
- Release Version 2.12
- Release Version 2.11
- Release Version 2.10
- Release Version 2.09
- Release Version 2.08
- Release Version 2.07
- Release Version 2.06
-
2022 Releases
- Release Version 2.05
- Release Version 2.04
- Release Version 2.03
- Release Version 2.02
- Release Version 2.01
- Release Version 2.00
- Release Version 1.99
- Release Version 1.98
- Release Version 1.97
- Release Version 1.96
- Release Version 1.95
- Release Version 1.93 & 1.94
- Release Version 1.92
- Release Version 1.91
- Release Version 1.90
- Release Version 1.89
- Release Version 1.88
- Release Version 1.87
- Release Version 1.86
- Release Version 1.84 & 1.85
- Release Version 1.83
- Release Version 1.82
- Release Version 1.81
- Release Version 1.80 (Jan-24-2022)
- Release Version 1.79 (Jan-03-2022)
-
2021 Releases
- Release Version 1.78 (Dec-20-2021)
- Release Version 1.77 (Dec-06-2021)
- Release Version 1.76 (Nov-22-2021)
- Release Version 1.75 (Nov-09-2021)
- Release Version 1.74 (Oct-25-2021)
- Release Version 1.73 (Oct-04-2021)
- Release Version 1.72 (Sep-20-2021)
- Release Version 1.71 (Sep-09-2021)
- Release Version 1.70 (Aug-23-2021)
- Release Version 1.69 (Aug-09-2021)
- Release Version 1.68 (Jul-26-2021)
- Release Version 1.67 (Jul-12-2021)
- Release Version 1.66 (Jun-28-2021)
- Release Version 1.65 (Jun-14-2021)
- Release Version 1.64 (Jun-01-2021)
- Release Version 1.63 (May-19-2021)
- Release Version 1.62 (May-05-2021)
- Release Version 1.61 (Apr-20-2021)
- Release Version 1.60 (Apr-06-2021)
- Release Version 1.59 (Mar-23-2021)
- Release Version 1.58 (Mar-09-2021)
- Release Version 1.57 (Feb-22-2021)
- Release Version 1.56 (Feb-09-2021)
- Release Version 1.55 (Jan-25-2021)
- Release Version 1.54 (Jan-12-2021)
-
2020 Releases
- Release Version 1.53 (Dec-22-2020)
- Release Version 1.52 (Dec-03-2020)
- Release Version 1.51 (Nov-10-2020)
- Release Version 1.50 (Oct-19-2020)
- Release Version 1.49 (Sep-28-2020)
- Release Version 1.48 (Sep-01-2020)
- Release Version 1.47 (Aug-06-2020)
- Release Version 1.46 (Jul-21-2020)
- Release Version 1.45 (Jul-02-2020)
- Release Version 1.44 (Jun-11-2020)
- Release Version 1.43 (May-15-2020)
- Release Version 1.42 (Apr-30-2020)
- Release Version 1.41 (Apr-2020)
- Release Version 1.40 (Mar-2020)
- Release Version 1.39 (Feb-2020)
- Release Version 1.38 (Jan-2020)
- Early Access New
Workday RaaS (Edge)
Workday is a cloud-based enterprise platform for human resources, finance, and planning. Its Report-as-a-Service (RaaS) feature lets you publish custom reports as web services, so that external applications can read the report results through a URL.
Hevo uses the Workday RaaS web service to replicate the data of your Workday custom reports to the Destination of your choice. Each report that you add to the Pipeline is loaded to a separate table in the Destination. To ingest data, you must provide Hevo with the username and password of a Workday Integration System User (ISU) and the URL of each report.
Supported Features
| Feature Name | Supported |
|---|---|
| Capture deletes | Yes (for reports without dynamic parameters) |
| History mode | No |
| Custom data (user-configured tables & fields) | Yes |
| Data blocking (skip objects and fields) | Yes |
| Resync (objects and Pipelines) | Yes |
| API configurable | Yes |
Prerequisites
-
An active Workday account from which data is to be ingested.
-
You have the permissions to create an Integration System User and security groups in Workday, to create the Integration System User.
-
One or more Workday custom reports of the Advanced type, with Enable As Web Service selected, to obtain the report URL.
Obtain the Workday Credentials
Hevo connects to Workday with the username and password of an Integration System User, and reads data from the URL of each report. Workday lets you publish custom reports as web services, so that their results are available through a URL.
Create an Integration System User
Perform the following steps to create the user with which Hevo connects to Workday:
-
Log in to your Workday account as an administrator.
-
Search for and run the Create Integration System User task.

-
Specify a username and password for the user, select Do Not Allow UI Sessions, and then click OK. Save the username and password securely.

-
Search for and run the Create Security Group task. Create a security group of the Integration System Security Group (Unconstrained) type, and add the Integration System User to it.
-
Grant the security group Get access to the domain security policies of the data in your reports. For example, to ingest worker data, grant access to the Worker Data domains that the report uses.
-
Search for and run the Activate Pending Security Policy Changes task to apply the changes.
Share the Report and Obtain the Report URL
Perform the following steps for each report that you want to ingest:
-
Edit the custom report, and ensure that the report type is Advanced. On the Advanced tab, in the Web Services Options section, ensure that Enable As Web Service is selected.

-
On the Share tab of the report, share the report with the Integration System User.
-
Search for the report. Click the related actions icon next to the report name, and then click Web Service > View URLs.

-
On the View URLs Web Service page, right-click the JSON or CSV link, copy the link address, and save it. The URL has the form https://<host>/ccx/service/customreport2/<tenant>/<report owner>/<report name>?format=json.

-
(Optional) To ingest only the changed data of a report in each Pipeline run, the report must have date prompts, such as a start date and an end date. Note the names of these prompts as they are shown in the report URL, for example, Start_Date and End_Date.
Note: If the password of the Integration System User changes or the user is disabled, Hevo cannot connect to Workday, and the Pipeline stops ingesting data. To resume ingestion, modify the Source configuration with valid credentials.
Configure Workday RaaS as a Source in your Pipeline
Perform the following steps to configure your Workday RaaS Source:
-
Click Pipelines in the Navigation Bar.
-
Click + Create Pipeline in the Pipelines List View.
-
On the Select Source Type page, select Workday RaaS.
-
On the Select Destination Type page, select the type of Destination you want to use.
-
In the Configure Source screen, specify the following:

-
Source Name: A unique name for your Source, not exceeding 255 characters. For example, Workday RaaS Source.
-
In the Connect to your Workday account section, specify the following:
-
Workday Username: The username of the Integration System User that you created.
-
Workday Password: The password of the Integration System User.
-
-
In the Report Configuration section, click Add Report, specify the following, and then click Save. Repeat this step for each report that you want to ingest. You can add up to 25 reports.

-
Table Name: The name of the Destination table for the report. The name must start with a letter, contain only letters, numbers, and underscores, and be unique across reports. You cannot change it after you create the Pipeline. For example, employee_data.
-
Report URL: The URL of the report that you copied from Workday.
-
Report Format: The format of the report data. Select JSON or CSV. The format must match the format value in the report URL. If the URL does not contain a format value, Hevo appends the selected format to it. Default value: JSON.
-
Enable Dynamic Parameters: Select Enabled to ingest only the data in a date range in each Pipeline run. Hevo passes the dates to the date prompts of the report. Default value: Disabled. If you select Enabled, specify the following:
-
Report Start Date Prompt Name: The name of the prompt that filters the report by start date, exactly as it is in Workday. For example, Start_Date.
-
Report End Date Prompt Name (Optional): The name of the prompt that filters the report by end date, exactly as it is in Workday. For example, End_Date. Leave this field blank if the report has only one date prompt.
-
Report Start Date: The date from which Hevo ingests data in the first Pipeline run, in the MM/DD/YYYY format. For example, 01/15/2024. The date cannot be later than the current date or earlier than 01/01/1990.
-
Sync Strategy: The date range that Hevo ingests in each subsequent Pipeline run. Select one of the following:
-
Sync updates from last sync: Hevo ingests data from the date of the last Pipeline run to the current date. As a result, the data of the day of the last run is ingested again and merged with the existing records. This is the default value.
-
Sync updates from report start: Hevo ingests data from the Report Start Date to the current date in each Pipeline run.
-
-
-
Enable Unpacking Nested Columns: If enabled, Hevo loads each field of a nested JSON object to a separate column. Else, Hevo loads the nested object as a JSON string. Lists are always loaded as JSON strings. Default value: Disabled.
-
Use Hevo Generated Primary Key: If enabled, Hevo generates the primary key of each record from the values of all its columns. Enable this option if no column or combination of columns uniquely identifies a record in the report. You cannot use this option with dynamic parameters. Default value: Disabled.
-
-
In the Primary Key Selection section, select one or more columns that uniquely identify each record of a report. Each tab shows the columns of one report. Reports for which you enabled Use Hevo Generated Primary Key are not shown.
-
-
Click Test & Continue to test the connection to your Workday RaaS Source. Once the test is successful, you can proceed to set up your Destination.
When you click this button, Hevo checks the following for each report:
-
The Integration System User can access the report URL.
-
The report returns data in the format that Workday RaaS uses.
-
A primary key is selected, or Use Hevo Generated Primary Key is enabled.
-
If dynamic parameters are enabled, the prompt names match the prompts of the report, and the report start date is valid.
-
Data Replication
Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. Each report that you add to the Pipeline is an object. By default, all the reports are selected. However, you can modify this selection while creating or editing the Pipeline.
Hevo ingests the data of each report as per the sync frequency, as follows:
-
Reports without dynamic parameters: Hevo ingests all the data of the report in each Pipeline run.
-
Reports with dynamic parameters: In the first Pipeline run, Hevo ingests the data from the Report Start Date to the current date. In each subsequent run, Hevo ingests the data as per the sync strategy that you selected for the report. Hevo passes the dates to the report prompts in the YYYY-MM-DD format.
You can resync each report.
If Workday rejects a request because too many requests were made, or because the service is temporarily unavailable, Hevo retries the request up to three times, at intervals of 30 seconds. Workday limits the number of requests for each tenant based on the number of workers. For example, for a tenant with fewer than 3,500 workers, Workday allows up to 15,000 requests per hour and 75,000 requests per day. For a tenant with more than 100,000 workers, Workday allows up to 100,000 requests per hour and 350,000 requests per day. To understand how Hevo handles such scenarios, read Handling Rate Limit Exceptions.
Note: You can create a Pipeline with this Source only using the Merge load mode. The Append mode is not supported for this Source.
Schema and Primary Keys
Hevo discovers the columns of each report from the first record that the report returns. As a result, the schema of each Destination table depends on the fields in your Workday report. Hevo loads the data of all the columns as text (VARCHAR).
The primary key of each table is the set of columns that you select in the Primary Key Selection section. If you enable Use Hevo Generated Primary Key for a report, Hevo adds the _hevo_generated_pk column to the table and uses it as the primary key.
Data Model
The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:
| Object | Description |
|---|---|
| Report | Contains the data of a Workday custom report that you add to the Pipeline. Hevo creates one table for each report that you add, with the name that you specify in the Table Name field. |
Additional Information
Read the detailed Hevo documentation for the following related topics:
Handling of Deletes
For reports without dynamic parameters, Hevo uses a full data refresh approach to capture delete actions. During each Pipeline run, Hevo compares the data fetched from the report with the data present in the Destination table. If a record exists in the Destination but is no longer returned by the report, the record is marked as deleted by setting the value of the metadata column __hevo__marked_deleted to True.
For reports with dynamic parameters, Hevo does not capture deletes. Records that are deleted in Workday, or no longer returned by the report, remain in the Destination.
Source Considerations
-
Workday does not return the fields that are empty for a record. As Hevo discovers the columns from the first record of the report, it does not create a column for a field that is empty in that record, and does not load the data of that field.
-
If a primary key column of a record is empty, Hevo does not load the record to the Destination and reports it as an error record.
-
Hevo does not check whether the primary key columns that you select are unique for each record. If multiple records of a report have the same primary key values, Hevo merges them, and only one of them remains in the Destination. To avoid this data loss, select primary key columns that uniquely identify each record, or enable Use Hevo Generated Primary Key, and then resync the report.
-
Hevo does not retain the primary key columns that you selected for a report. If you edit the report in the Source configuration, select its primary key columns again in the Primary Key Selection section.
-
Hevo loads the fields that contain multiple values, such as lists, as JSON strings, even if you enable Enable Unpacking Nested Columns.
-
Workday does not export reports larger than 2 GB. If a report exceeds this limit, enable dynamic parameters for the report so that Hevo ingests the data in smaller date ranges, or add filters to the report in Workday.
-
Workday is unavailable during its weekly scheduled maintenance on Friday nights (Pacific Time). Pipeline runs during this period fail, and Hevo ingests the data in the next run.
Revision History
Refer to the following table for the list of key updates made to this page:
| Date | Release | Description of Change |
|---|---|---|
| Oct-18-2026 | NA | New document. |