Workday Reports connector FAQs
This page answers frequently asked questions about the Workday Reports connector in Databricks Lakeflow Connect.
General managed connector FAQs
The answers in Managed connector FAQs apply to all managed connectors in Lakeflow Connect. Keep reading for Workday-specific FAQs.
Connector-specific FAQs
The answers in this section are specific to the Workday Reports connector.
Which Workday products does the connector support?
The connector supports Workday Reports-as-a-Service (RaaS).
How does Databricks connect to Workday?
Databricks retrieves data from Workday using Reports-as-a-Service (RaaS) by calling the report URL over HTTPS. Credentials are stored securely inside Unity Catalog and can only be retrieved if the user running the ingestion flow has appropriate permissions. You can optionally create a specific user in Workday for Databricks ingestion.
How many Workday reports can be ingested in a pipeline?
Databricks recommends limiting one Workday pipeline to 250 reports. If you need to ingest more reports, you can create multiple pipelines.
How does the connector handle Delta-incompatible data types?
Lakeflow Connect automatically transforms Workday data types to Delta-compatible data types. See Workday Reports connector reference.
What happens if I run an incremental pipeline update before all of that day's records have been ingested?
The connector has a one-day overlap between runs. On the next pipeline update, it starts from the same day where it left off — reading but ignoring any rows that it already ingested.
What happens if I don't specify a cursor (sequence_by) key?
If a sequence_by key is not specified, the connector automatically adds a column called _databricks_ingested_at, which stores the timestamp indicating when each row was ingested. In subsequent runs, the connector ingests all new inserts since the last recorded _databricks_ingested_at timestamp.
Can I use a single prompt instead of two for incremental ingestion?
Yes, you can use a single prompt (for example, Date_Greater_Than_Or_Equal_To) as long as it is defined on a date column and is inclusive. Make sure to specify the cursor key (sequence_by) when using the coalesce expression for the prompt value.
How do I find the correct XML alias for my Workday prompts?
The display value for prompts in the Workday URL generation form is not necessarily the actual name of the prompts. You need the true XML alias, which is the parameter name that appears in the report URL. Check the report definition in Workday to find the XML alias for each prompt.