Skip to main content

logoCorrectSize.png

Workday Adaptive Planning KB

Multi-Instance Data Synchronization Methods

Introduces and compares the different methods of synchronizing data and metadata across multi-instance configurations.

You can link multiple instances for a single organization into multi-instance or multi-domain setups. Multi-instance setups satisfy use cases for:

Functional Planning

Your organization wants separate instances for functional planning outside of your financial planning instance. Typical functional planning needs include:

  • Sales planning
  • Workforce planning
  • Marketing planning 

Department Level Planning

Your large departments within your organization want to manage their individual budgeting and planning lifecycles. By giving departments full control over who manages and accesses their plans, your departments maintain control. Department plans can then be shared with other departments or corporate planners.

Synchronizing Data and Metadata Across Instances

A multi-instance setup can address different planning needs within the same organization. Organizations typically want to synchronize data between their different instances. As an example, departmental expenses calculated in child instances may need to roll up to the parent instance for corporate-level reporting.

You may also want to synchronize metadata across instances. As an example, you may want all instances to keep the same chart of accounts. You would also want all of the changes to accounts to synchronize across all of your instances. Metadata changes would cascade from a parent instance where the accounts are managed. The remaining instances in the hierarchy pick up those changes.

You can use these methods for synchronizing across a multi-instance configuration:

Linked Level Refresh

When an instance is part of a multi-instance setup,  you can configure data synchronization from a child instance to a parent. You link a level in the child instance to a level in the parent instance. You can also set up how dimension values map when data flows through the linked instances.

See Create Linked Levels for Multi-instances

Integration Framework

The Integration framework can transfer data and metadata between instances. With integration, you can use the Planning data source to export:

  • Standard sheet data
  • Cube sheet data
  • Modeled sheet data
  • Account metadata
  • Level metadata
  • Dimension metadata
  • Attribute metadata

The data/metadata that exports to the staging area can load into the current instance with loaders. The data/metadata can also load into a different instance or a third party system through a custom cloud loader.

See Integration Workflow

Linked Modeled Sheet Refresh (Sales Planning Only)

If you have Sales Planning, you can move data between modeled sheets across instances when specific conditions on the modeled sheets are met.

See Create Modeled Sheet Links.

Comparison of Multi-Instance Synchronization Methods

Use this table to help you understand the different data and metadata synchronization methods for your multi-instance setup.

  Linked Level Refresh Integration Framework Linked Modeled Sheets
(Sales Planning only)
Data synchronization from child to parent instances yes yes no
Data synchronization from parent to child instances no yes no
Data synchronization across sibling instances no yes no
Data synchronization across modeled sheets no yes

Requires matching columns and dimension values with matching names on both instances.

Does not support:

  • Level attributes
  • Dimension attributes
  • Account attributes
  • Column types:
    • Text selector
    • Initial balance
    • Model sheet account (Display Column)
Data synchronization across cube sheets no yes no
Data synchronization across standard sheets yes yes no
Data transformation during synchronization no yes no
Metadata syncrhonization across instances no yes no
Integration implementation project needed for multi-instances no yes no
Automated (scheduled) synchronization no yes no

 

  • Was this article helpful?