Workday Adaptive Planning Private Preview
Workday Adaptive Planning provides budgeting, forecasting, reporting, and analytics for businesses of all sizes.
Features
Feature Name | Supported | Notes |
---|---|---|
Capture deletes | check | ACCOUNT , ACCOUNT_ATTRIBUTE_MAPPING , ATTRIBUTE , ATTRIBUTE_VALUE , CURRENCY , DIMENSION , DIMENSION_VALUE , DIMENSION_VALUE_PROPERTY , DIMENSION_VALUE_ATTRIBUTE_MAPPING , DIMENSION_VALUE_MAPPING , LEVEL , LEVEL_ATTRIBUTE_MAPPING , and VERSION tables. |
History mode | ||
Custom data | check | |
Data blocking | check | |
Column hashing | check | |
Re-sync | check | |
API configurable | check | API configuration |
Priority-first sync | ||
Fivetran data models | ||
Private networking | ||
Authorization via API | check |
Setup guide
Follow our step-by-step Workday Adaptive Planning setup guide to connect Workday Adaptive Planning with your destination using Fivetran connectors.
Sync overview
In every sync, we extract the metadata tables and custom reports from your Workday Adaptive Planning account. The metadata tables include information about the structure of your data, such as, accounts, levels, dimensions, attributes, currency, and versions. The custom reports contain the actual data you have defined in your Workday Adaptive Planning reports.
We perform full re-imports for both metadata tables and custom reports.
Schema information
This schema applies to all Workday Adaptive Planning connections.
Schema notes
We sync metadata tables along with custom reports from your Workday Adaptive Planning account. The ERD above shows the metadata tables and an example custom report table. The actual custom report tables depend on the reports you have created in your Workday Adaptive Planning connector setup account.
For custom reports, we receive the data from the Workday Adaptive Planning API in wide format. For example:
Account Name | Account Code | Level Name | Actor | FY_2023 | FY_2024 | FY_2025 |
---|---|---|---|---|---|---|
Customer 2 | dCF_Custmr2 | Sales - Auckland | Customer | 0 | 0 | 483199.474 |
Customer 2 | dCF_Custmr2 | Services - Australia | Customer | 0 | 0 | 327603.3699 |
We transform the data into long format to make it easier to analyze over time. The transformation involves unpivoting the fiscal year columns into a single time
column and corresponding value
column.
Here is the data in long format:
Account Name | Account Code | Level Name | Actor | Time | Value |
---|---|---|---|---|---|
Customer 2 | dCF_Custmr2 | Sales - Auckland | Customer | FY_2023 | 0 |
Customer 2 | dCF_Custmr2 | Sales - Auckland | Customer | FY_2024 | 0 |
Customer 2 | dCF_Custmr2 | Sales - Auckland | Customer | FY_2025 | 483199.474 |
Customer 2 | dCF_Custmr2 | Services - Australia | Customer | FY_2023 | 0 |
Customer 2 | dCF_Custmr2 | Services - Australia | Customer | FY_2024 | 0 |
Customer 2 | dCF_Custmr2 | Services - Australia | Customer | FY_2025 | 327603.3699 |
Custom reports primary key
For custom reports, we create a composite primary key using the predefined columns and custom dimensions selected by the user.
Predefined columns include:
version_name
account_name
account_code
level_name
time
Custom dimensions include, dimensions that are selected by the user.
Adding or removing the dimensions columns results in a change in the primary key and hence requires a hard delete of existing data. The subsequent resync is count towards free MAR.