In This Article

Overview

Importing from Template

Importing Linked VDTs from Value Hound

Special Considerations

Summary


Overview

Value Driver Trees (VDTs) can be imported into Ideas/Initiatives to save time and ensure consistency across your organization. Instead of manually creating complex VDT structures from scratch, you can reuse existing VDTs or import pre-configured VDT templates. For more information on prerequisites, adding and importing from the VDT Library, refer to VDT Library and Template Management: Adding to and Importing from VDT Library Part 1 article


Importing from Template

The Import from Template option allows you to import VDT structures from a pre-configured Excel file. This is ideal for standardized VDT structures that you use repeatedly.


Step-by-Step Instructions

Step 1: Open the Import Dialog

  • Click the library icon in the VDT toolbar
  • Select Import from Template
  • A pop-up dialog will appear


Step 2: Download the Template

If you don't have a template yet:

  1. Click Download Template in the dialog
  2. An Excel file will download to your computer
  3. This template shows the required format for VDT imports


Step 3: Prepare Your Template File

The Excel template must include the following required fields:

  • Title: The display name for each node
  • Node Type: Parent, KPI, Constant, Variable, or Reference
  • Reference Character: The letter/character used in formulas (e.g., A, B, C)
  • Formula/Expression: How the node calculates for parent nodes (e.g., =A*B)
  • Values: Baseline and target values for constant, variable and KPI nodes

 

Template Best Practices:

  • Use clear, descriptive node names
  • Maintain consistent reference characters
  • Test formulas before importing
  • Document any special configurations

For more information on how to populate the template, please see this Rules and Samples article: Idea Value Driver Tree Import Rules and Sample : Helpdesk


Step 4: Configure Import Settings

    1. Replace Existing VDT Tree Checkbox

  • Check to replace your entire current VDT
  • Leave unchecked to import into a specific parent node

    2. Select Import To Node

  • Choose the empty parent node for the import
  • This is where your template structure will be inserted

     

    3. Select Template File

  • Click Choose File or Browse
  • Navigate to your prepared Excel template
  • Select the file and click Open


Step 5: Complete the Import

  • Click Import to process the template

     
  • While the system validates the template structure, the following notifications will appear


  • You can verify whether the import was successful or not by viewing the import status from your notifications panel


  • If successful, the VDT structure appears in your selected parent node

Importing Linked VDTs from Value Hound

When importing VDTs from the Value Hound module into an Idea/Initiative VDT, special considerations apply because Value Hound supports linked VDTs (VDTs that reference other VDTs), but Ideas/Initiatives do not.


What is a Linked VDT?

  • A linked VDT is a VDT that contains nodes referencing another complete VDT
  • This creates a parent-child relationship between VDTs
  • Common in Value Hound for complex organizational structures

Step-by-Step Instructions

Step 1: Start the Import

  • Follow the same steps as "Import from Library" above
  • Select a Value Hound VDT from the dropdown

Step 2: Review the Warning

  • If the Value Hound VDT imported into an Idea/Initiative VDT contains linked nodes, a warning message appears that states:
    • The system detects linked child nodes
    • A warning explains that linked nodes will be converted
    • You can choose to continue or cancel


Step 3: Decide to Continue or Cancel

  • Continue: The linked child nodes will be converted and the following occurs:
    • Linked child nodes become constant nodes on the Idea/Initiative VDT
    • The current values from the linked VDT are captured
    • The connection to the original VDT is removed
  • Cancel: No changes are made

Step 4: Verify After Import

  • Check that converted constant nodes have correct values
  • Update values manually if needed


Impact on Your VDT

  • Calculations: Will use the captured constant values
  • Updates: Changes to the original Value Hound VDT won't affect your Idea/Initiative VDT
  • Editing: You can manually update the constant values as needed

The link to the referenced VDT will still be maintained on the Value Hound VDT if a linked Value Hound VDT is imported to another Value Hound VDT. The conversion to a constant node only occurs when a linked Value Hound VDT is imported to an Idea/Initiative VDT.



Special Considerations

Emissions Nodes

When importing a VDT that contains Emissions nodes (non-financial benefit nodes tagged to the Emissions category):

  • An info message will appear during import that states that the initiative will be sourced to the Emissions module
  • This means the Idea's emissions data will feed into organization-wide emissions tracking
  • Note: This message only appears when the Emissions feature is enabled on your site



Summary

VDT Node Types After Import

Original Node Type

After Import

Notes

Parent Node

Parent Node

Structure preserved

KPI Node

KPI Node

KPI connection maintained

Constant Node

Constant Node

Values preserved

Variable Node

Variable Node

Configuration maintained

Reference Node

Reference Node

References preserved if target exists

Linked VH VDT Node

Constant Node (when imported into an Idea/Initiative VDT

⚠️ Converted, connection removed


Import Methods Comparison

Method

Best For

Requirements

Key Benefits

Limitations

Import from Library

Reusing existing Initiative or Value Hound VDTs

Same folder structure, source VDT exists

Maintains node types and KPI connections

Limited to available VDTs in your structure

Import from Template

Bulk imports, standardized structures

Excel template file

Flexible, repeatable, version-controlled

Requires manual template preparation

Linked VH VDT Import

Importing Value Hound VDTs

Value Hound module active

Cross-module integration

Linked nodes convert to constants