In This Article

Overview

VDT Library

What Happens After Import

Why This Matters

Next Steps

Overview

Once you have built and populated a Value Driver Tree with data, you can store it in the VDT Library for reuse and import it into other Value Driver Trees.

Prerequisite:
You must have the Contribute to VDT Library role permission enabled to add and import VDTs. This permission is found in the Administration tab.


VDT Library

Step 1: Add a VDT to the Library

  1. Open the completed Value Driver Tree
  2. Select the library (open book) icon in the VDT toolbar


  3. Choose Add to Library option


  4. Enter a Name and Description of the VDT


  5. A confirmation box displays indicating that primary fields (Actual, Target, Baseline) will be added to constant nodes


  6. Confirm by selecting Continue to save the VDT to the Library

The stored VDT now appears in the Import from Library list.

 

Step 2: Import a VDT from the Library

  1. Open the target Value Driver Tree where you want to import another VDT
  2. Select the library icon in the VDT toolbar


  3. Choose Import from Library

  4. Tick Replace existing tree if you want to replace the current tree entirely


  5. From the Import from VDT list, select the VDT you want to import


  6. Choose the parent node where the VDT will be imported to and the parent node which the VDT will be imported from

  7. Confirm the import when prompted

The imported structure is copied into the target tree, preserving node types, formulas, and KPI connections.

 

Step 3: Import from a Template (Optional)

You can also import a VDT from a file template:

  1. Select the library icon and then choose Import from template

  2. Ensure you have the template file stored locally
  3. Tick Replace existing treeif you want to replace the current tree entirely


  4. Click Select File and choose your template file


  5. After selecting the file, click Import

If you don't have a template yet, you can download one from the import dialog.

What Happens After Import

  • Imported nodes appear under the selected parent node in the tree
  • KPI nodes remain connected to their original KPIs
  • Constant nodes retain their values and formulas
  • You can immediately edit imported structures as needed

 

Why This Matters

Storing VDTs in the library and importing them allows you to:

  • Reuse validated models across multiple initiatives
  • Maintain consistency in calculation logic
  • Save time by avoiding repeated manual builds

This completes the core creation and reuse lifecycle for Value Driver Trees.

Next Steps

To learn how to edit and structure your Value Driver Tree, see: