Workday Reports connector limitations

Preview

LakeFlow Connect is in gated Public Preview. To participate in the preview, contact your Databricks account team.

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

General limitations

  • When you run a scheduled pipeline, alerts don’t trigger immediately. Instead, they trigger when the next update runs.

  • 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 Delta Live Tables behavior.

  • When you select a schema, you are selecting not only the CURRENT tables but also the FUTURE tables that get added to it.

  • During maintenance periods, Databricks might not be able to access your data.

  • If the source table name conflicts with an existing destination table name, the flow fails.

  • Databricks can only ingest reports with less than 2 GB of data and less than 1M records.

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

  • Column-level selection and deselection are not supported.

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

Authentication limitations

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