Workday Reports connector limitations

This article lists limitations and considerations for connecting to and ingesting from Workday using Lakeflow Connect.

General limitations

When a source table is deleted, the destination table is not automatically deleted. You must delete the destination table manually. This behavior is not consistent with DLT behavior.
During source maintenance periods, Databricks might not be able to access your data.
If a source table name conflicts with an existing destination table name, the pipeline update fails.
Multi-destination pipeline support is API-only.
You can optionally rename a table that you ingest. If you rename a table in your pipeline, it becomes an API-only pipeline, and you can no longer edit the pipeline in the UI.
Column-level selection and deselection are API-only.
If you select a column after a pipeline has already started, the connector does not automatically backfill data for the new column. To ingest historical data, manually run a full refresh on the table.

The Workday APIs do not support ingesting reports with more than 2 GB of data or more than 1M records. Your organization’s Workday API limits might be lower than this.
Full refresh is supported, but incremental refresh is not, so Databricks ingests the full report every time the pipeline runs. However, you can choose whether to overwrite the destination tables or merge with the existing data. When you choose to merge the data, you can also select between SCD type 1 and SCD type 2.
Workday’s Human Capital Management (HCM) product is not supported.
Databricks automatically transforms data for compatibility with Delta.
Incremental report ingestion is not supported.
Ingestion pipeline creation is only available using the Pipelines API. You can’t create a Workday Reports ingestion pipeline in the Databricks UI.
The connector doesn't support the ingestion of reports with duplicate primary keys.

Username and password must be reset every 90 days.
There are two tokens: the refresh token and the access token. These tokens are typically created on behalf of a Workday integrated system user (ISU), but this is not required.
- With the refresh token, the user has the option to let it expire or not. If it does expire, then you have to edit the connection.
- The refresh token does not automatically change when you update your username or password. The only thing that can make a non-expiring refresh token expire is if the credentials or access level for the associated ISU is reduced.
- With the access token, the user doesn’t have the option to let it expire, but you can customize how long it takes.