Importing a User Defined Dimension

When you import data for a dimension in a Universal application, you import nodes and their property values. If the dimension is a hierarchy, the import also specifies parent-child relationships between the nodes.

Before you begin:

• See Importing Dimensions for import options, considerations, and information on import modes.

• When you import properties that use Boolean values the following rules apply:

  • If the value in the import file matches the Boolean True or Boolean False Value property definition parameter, then that value is used.

  • Otherwise, if the value in the import file is 1, T, True, Y, or Yes then True is used for the value.

  • Otherwise, False is used for the value.

• You can import data only into properties for which the Sync Direction is set to either Import or Both. To review or modify properties, see Modifying a Property for a Node Type in a User Defined Dimension.

• When you import to an existing dimension in Merge or Replace mode, the system checks the node type of the nodes that you are importing, as follows:
  • For applications that do not have a node type column:
    • If the node already exists in the bound dimension, the system finds and uses the existing node and node type when it runs the import.
    • If the node does not already exist in the bound dimension, the system imports the node using the default node type (if the node does not have children) or default parent node type (if the node does have children).
  • For applications that have a node type column, that column is used to create the node during import, as follows:
    • If the node type for the node in the import file is valid for this viewpoint, the node type in the import file is used. A node type is valid for a viewpoint if it is used in the hierarchy set or node set.
    • If the node type for the node in the import file is not valid for this viewpoint, the record is skipped.
    • If the node type for the node in the import file is blank, the system imports the node using the default node type (if the node does not have children) or default parent node type (if the node does have children)..

      Note:

      If the default node type is not valid for the viewpoint, the system imports the node using the first valid node type alphabetically in the viewpoint.
  • For applications that have a parent node type column, if your dimension contains multiple nodes that have the same name but different node types, the parent node type column is used to locate the node during import, as follows:
    • If the node type for the node in the import file is valid for this viewpoint, it is used to find the node in the node type. If the node cannot be found, the record is skipped.
    • If the node type for the node in the import file is not valid for this viewpoint, the record is skipped.
    • If the node type for the node in the import file is blank, the system uses the logic in the previous bullet for default node and default parent node to try to locate the correct parent. If the parent cannot be determined using this logic, the record is skipped.

1. Create the import file, see Import and Export File Format for User Defined Dimensions.
2. Click Applications.
3. In the Actions column for the application, click , and then select Import.
4. In the Dimensions section, click the dimension into which you will import data.
5. Specify the import file.
   The File Name text box displays the name of the import file.
6. In Import Mode, select Merge, Replace, or Reset. See Importing Dimensions for details on import modes. .
7. Optional: In the Summary section, click the dimension name to inspect the dimension and view the import options. Close the inspector dialog to return to the import screen.
8. Click Import.
   A message indicating the data was successfully imported is displayed.
9. Check the Messages text box to see if any rows could not be imported. If so, fix the issues and then repeat these steps.