Anaplan connector FAQ
This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Databricks previews.
This page answers frequently asked questions about the managed Anaplan ingestion connector in Lakeflow Connect. For FAQs that apply to all managed connectors, see Managed connector FAQs.
Which tables does the connector support?
The connector supports the audit_events and users tables. For the schema of each table, see Supported source tables.
Does the connector support incremental ingestion?
Yes, for the audit_events table, using the createdDate cursor field. The connector refreshes the users table with a full snapshot on each pipeline update.
How far back can the connector ingest data?
For the incremental audit_events table, the first sync ingests events from the previous 365 days, and each later sync ingests events created after the last run. To ingest from a specific start time, set the start_datetime connector option. See Connector options. The users table reingests all records on every run.
Anaplan retains audit events for a limited period — up to 30 or 90 days, depending on your edition — so the earliest events the connector can ingest are bounded by Anaplan's retention window, not the 365-day connector default. See Audit.
Which authentication methods does the connector support?
The connector authenticates with an Anaplan CA certificate and its paired private key, and exchanges them for a short-lived access token automatically. OAuth U2M, OAuth M2M, and basic username/password authentication are not supported.