Passer au contenu principal


Adaptive Insights French

Differences between cloning levels and creating new levels

This article includes suggestions and workarounds. Content may not be accurate for all use cases or represent best practices for the latest release.


What is the difference between cloning Levels and creating new Levels?


Creating a New Level

This option creates a new Level as a child of the currently selected Level.

Details that are inherited from the Parent Level:

    • Shared formulas in unlocked Versions. 
    • The sheet availability will initially be inherited from the Parent Level. This can be modified in the new Level details before saving the Level.
    • User Level Access
    • Currency Settings
    • Attribute Values
    • Version Availability
    • Workflow status

Details that are not inherited from the Parent Level:

    • Hard-coded values, formulas, sheet notes, and cell notes
    • The Audit Trail 
    • Use within Rules
    • Import or Export mappings
    • Availability within report Parameters.

Cloning a Level

This option creates a Clone Level as a sibling of the currently selected Level.

Details that are inherited from the Source Level:

    • Hard-coded data and formulas in all unlocked Plan Versions. Data will not be copied in the Actuals Version.
    • Sheet notes and Cell Notes in all Versions
    • Shared formulas on the Actuals and unlocked Plan Versions. If the "Rolls up to" field is changed during the creation of the Clone, the shared formuals will be inherited from the new Parent Level.
    • Use in all Rules for all Versions
    • Export Mapping
    • User Level Access
    • Availability in any report Parameters in which the Source Level was available.

Details that are not inherited from the Source Level:

    • The Audit Trail 
    • Import  mapping 
    • The Clone will not replace a Source level on Reports. Reports which contain only the Source Level would need to be updated.
    • Workflow Status


In most cases, the "New Level" option will be used. Cloning a Level would typically be used in the following scenarios.

1. A user wants to create a New Level as a copy of a similar level:

This often happens when customers have things like projects or products built into the Organization Structure. Keep in mind the Actuals data will not be copied so that the Actuals values are not duplicated. The new project or product can be made unavailable in previous Versions.

2. A user wants to move the Department to another area of the Organization:

In this scenario, a copy of the Department would be created. The old Level would remain available in older Versions, while the new Level would only be available in new Versions. The old Level would also be made unavailable in the new Versions.


  • Cet article vous a été utile ?