Workday Activity Logging connector FAQ
This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Workday Activity Logging from the Previews page. See Manage Databricks previews.
Common questions about the managed Workday Activity Logging ingestion connector, including supported tables, the historical ingestion window, authentication, permissions, and SCD type 2 support. For FAQs that apply to all managed connectors, see Managed connector FAQs.
Which tables does the connector support?
The connector supports only the activity_logging table in the default source schema. For the destination schema, see Destination table schemas.
How far back can the connector ingest data?
For the first sync, the connector ingests up to the previous 30 days of activity log events. Each later sync incrementally ingests new events.
Which authentication method does the connector support?
The connector uses an OAuth client ID, client secret, and refresh token. The refresh token is generated for a Workday integration system user.
Which Workday permissions does the connector require?
The integration system security group must have View access under Report/Task Permissions and Get access under Integration Permissions for the System Auditing domain. You must activate pending security policy changes after granting these permissions.
Does the connector support SCD type 2?
No. The activity_logging table is append-only and doesn't support SCD type 2.
Which pipeline features aren't supported?
The connector doesn't support UI-based pipeline authoring, API-based row filtering, or automated schema evolution. For the complete feature availability matrix, see Feature availability.