Release Notes

August 2026

v1.0.2

PR #37 includes the following update.

Bug Fix

Fixes a bug where int_workday__employee_history failed to run if annual_currency_summary_primary_compensation_basis, annual_currency_summary_total_base_pay, or annual_currency_summary_total_salary_and_allowances weren't enabled. These fields are optional, so they now resolve to null when not synced instead of failing the model.

v1.0.3

Feature Updates

Adds DuckDB as a supported destination.

June 2026

v0.9.2

PR #33 includes the following update.

Bug Fix

Fixes an issue in stg_workday__worker_history where annual_currency_summary_primary_compensation_basis, annual_currency_summary_total_base_pay, and annual_currency_summary_total_salary_and_allowances could surface as strings instead of numeric values. These columns are now cast to float when the source type is a string.

v1.0.0

PR #34 includes the following updates.

Schema/Data Changes (--full-refresh required after upgrading)

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single Workday schema)	Empty string (`''`)	`<database>.<schema>`

Feature Updates

Introduces the new (recommended) workday_sources variable for more robust union data configuration. The old workday_union_schemas and workday_union_databases variables will still be supported. See the README for specific details.

Under the Hood

Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
Introduces fivetran_utils.partition_by_source_relation to conditionally include source_relation in partition clauses only when multiple sources are configured.

v1.0.1

PR #35 includes the following update.

Bug Fix

Fixes a runtime error in stg_workday__worker_history where annual_currency_summary_primary_compensation_basis, annual_currency_summary_total_base_pay, and annual_currency_summary_total_salary_and_allowances failed to cast when the value was non-numeric. These columns now resolve to null instead of erroring the run.

April 2026

v0.9.1

PR #31 includes the following update.

Under the Hood

Updates integration_tests/dbt_project.yml to ensure that the employee history models are generated in the docs and picked up by Quickstart.

March 2026

v0.8.2

Feature Updates

Updates the quickstart.yml:
- Adds workday__employee_daily_history, workday__monthly_summary, and workday__worker_position_org_daily_history to the list of public models.
- Adds supported_vars entry for employee_history_start_date to allow users to configure the employee history start date in Quickstart.
- Adds employee_history_enabled table variables for worker_history, worker_position_history, and personal_information_history to prevent missing sources from blocking downstream Quickstart models.

January 2026

v0.6.0

Features

Increases the required dbt version upper limit to v3.0.0.

v0.7.0

Schema and Data Changes

10 total changes • 0 possible breaking changes

Data Model(s)	Change type	Old	New	Notes
`workday__employee_overview`	Field added	N/A	`fivetran_id`	Added Fivetran composite key field to enable advanced joins with new schema updates. Field is null for legacy schema connections.
`stg_workday__personal_information_common_data`	New model	N/A	New staging model	New staging model for January 2026 Workday personal information schema update containing personal information fields including date and city of birth, nationality and blood type.
`stg_workday__country_personal_information`	New model	N/A	New staging model	New staging model for January 2026 Workday personal information schema update containing country-specific personal information fields including gender and marital status.
`stg_workday__military_service`	Join key changed	`worker_id` sourced from `personal_info_system_id`	`worker_id` sourced from `personal_info_common_id`	Model now uses updated `military_service` schema. Automatically uses `military_service_incoming` table if available for existing Fivetran connections, otherwise uses `military_service` table for new connections after January 5, 2026.
`stg_workday__military_service`	New columns	N/A	`discharge_type`, `status_id`	New fields available in updated schema.
`stg_workday__military_service`	Null legacy columns	`service_type`, `military_status`, `index`	`service_type`, `military_status`, `index` cast to null	Legacy fields cast to null for backward compatibility with updated schema.
`stg_workday__personal_information_ethnicity`	Join key changed	`worker_id` sourced from `personal_info_system_id`	`worker_id` sourced from `country_personal_information_id`	Model now uses updated `personal_information_ethnicity` schema. Automatically uses `personal_information_ethnicity_incoming` table if available for existing Fivetran connections, otherwise uses `personal_information_ethnicity` table for new connections after January 5, 2026.
`stg_workday__personal_information_ethnicity`	Null legacy column	`index`	`index` cast to null	Legacy field cast to null for backward compatibility with updated schema.

Note: These staging models are ephemeral and will not be present in the warehouse, but we felt it important to document these updates to capture the full depth of changes.

Feature Updates

Adds automatic table detection to support the newest version of the Workday API schema updates for new and existing Fivetran customers. Details in the Fivetran release notes:
- stg_workday__military_service automatically detects and uses military_service_incoming table for existing customers if available, otherwise uses military_service table for new customers.
- stg_workday__personal_information_ethnicity automatically detects and uses personal_information_ethnicity_incoming for existing customers table if available, otherwise uses personal_information_ethnicity table.
- All models maintain backward compatibility by setting legacy fields to null.
Added variables to enable table detection support. These variables are true by default to support existing customers, who will have the *_incoming tables available.
- workday__using_military_service_incoming
- workday__using_personal_information_ethnicity_incoming
If you're a new customer who set up a Workday HCM Fivetran connection after January 5, you should set these variables to false. See the README for more details.
Additionally, if customers need to leverage the old personal_information schema, they can set the below variable to false in the dbt_project.yml:
- workday__using_personal_info_v2_schema

Documentation

Updates DECISIONLOG with rationale for why we are not supporting the legacy schema.

Quickstart Updates

Adds table variables to support the above automatic table switching feature. Note: These will be removed after the transition period when table switching is no longer needed.

Under the Hood

Adds does_table_exist macro to dynamically detect table availability for automatic schema migration. Updates base models (stg_workday__military_service_base, stg_workday__personal_information_ethnicity_base) to use *_incoming table when available via automatic detection.
Updates int_workday__personal_details to automatically detect and use new split personal information tables when both are available.
Updates src_workday.yml with source definitions for new tables: personal_information_common_data, country_personal_information, plus _legacy variants for old schemas that will be deprecated after April.
Adds 4 integration test seed files for the new Workday personal information schema; renames seed files to keep reference to old military_service and personal_information_ethnicity schema; will deprecate after full transition to new tables in April 2026: workday_military_service_legacy_data, workday_personal_information_ethnicity_legacy_data.
Adds consistency tests for remaining Workday models.
Updates seed files to ensure proper validation of data downstream in workday__employee_overview.

v0.8.0

Documentation

Updates README with standardized Fivetran formatting.

Under the Hood

In the quickstart.yml file:
- Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.

v0.8.1

Test Fixes

Removes duplicate column definitions in YAML schema files to avoid dbt parse warnings.

August 2025

v0.5.0

dbt Fusion Compatibility Updates

Updated package to maintain compatibility with dbt-core versions both before and after v1.10.6, which introduced a breaking change to multi-argument test syntax (e.g., unique_combination_of_columns).
Temporarily removed unsupported tests to avoid errors and ensure smoother upgrades across different dbt-core versions. These tests will be reintroduced once a safe migration path is available.
- Removed all dbt_utils.unique_combination_of_columns tests.

Under the Hood

Updated conditions in .github/workflows/auto-release.yml.
Added .github/workflows/generate-docs.yml.