Mapping Dimensions

In the Map Dimensions section, use the following methods to specify how to import dimensions from the flat file, interface table or Data Relationship Management application. You can map dimensions by performing an automatic mapping or manual mapping.

  To map dimensions:

  1. To create new dimensions from the source, select Create Dimensions for the non-mapped dimensions with the source dimension name. For any dimension that is unmapped (that is, any dimension that is not automatically or manually mapped), the name of the dimension in the flat file, interface table, or Data Relationship Management application is the name used to create the new dimension.

    When you select “Create dimensions for the non-mapped dimensions...”, the Shared Library or application column is automatically populated.

  2. If a dimension in the flat file, interface table, or Data Relationship Management application exists in the Shared Library or application, automatically map the dimensions and select to merge the imported dimensions into the target dimension or replace the target dimensions with the imported dimension.

  3. To manually map the dimensions, in the Shared Library column, create a new dimension or map the imported dimension to another dimension. If mapping to another dimension, merge the imported dimension into the Shared Library dimension or replace the Shared Library dimension with the imported dimension. Perform one of these actions:

    • Select the Shared Library dimension to map to the imported dimension.

    • Create a dimension:

      1. From the Shared Library or application, select New Dimension.

      2. In the Add New Dimension dialog box, enter the dimension name and optional description, and click OK.

    • Optional: Select the Process Type.

      Note:

      If the target application contains the shared dimensions, then the Process Type does not display any options.

      • Merge as Primary—Merge as Primary processes all sections and adds new dimensions, members, relationships, properties and associations that exist in the source, but do not exist in the Shared Library or target application. No dimensions, members, relationships, properties, or associations are removed. If a dimension, relationship, member, or property specified in the source exists in the Shared Library or target application it is overwritten with the value specified in the source. (Members are not moved, but overwritten.) Properties not included in the source are unchanged in the Shared Library or target application.

        Note:

        If a member has multiple instances in a dimension, the IsPrimary column specifies which instance is primary and which instance(s) are shared. The IsPrimary parameter is optional; however, we strongly recommend that you use it. If left undefined, it defaults to “True”, which assumes that the member is primary. If you do not define the IsPrimary parameter or if there are duplicate members defined as primary, a warning is displayed in the Import Results file.

      • Merge as Move—This mode only processes members with IsPrimary set to true, and ignores any others. During processing, the first line specifying a primary location for a member is executed, any subsequent lines specifying a different primary location are ignored, and a warning message is displayed.

      • Replace—All new elements are added and all property updates are made. Then, any members or member relationships that are not specified in the source are deleted from the Shared Library or target application. You can also use replace mode to reorder members under a parent. Properties not included in the source are unchanged in the Shared Library or target application.

        This mode does not create new Shared members unless they are defined in the import file (IsPrimary=false). This mode can detect a primary member under a new parent and process it as a move.

        Note:

        The Replace option does not display the Reorder Type and Reorder Existing Members options.

  4. Select the Reorder Type.

    • Merge to Top—Places new imported child members at the beginning of the child list under their parent.

    • Merge to Bottom—Places new imported child members at the end of the child list under their parent.

  5. Select Reorder Existing Members.

    Select Reorder Existing Members to resort existing child members under a parent even when those members are not present in the import source. If “Merge to Top” is selected, the first child member in the import source becomes the first child under the parent, all imported child members are sorted to match the order in the import source, and any existing members not in the import source will be pushed to the end of the child list in their existing order. If “Merge to Bottom” is selected, the last child member in the import source becomes the last child under the parent, all imported child members are sorted to match the order in the import source, and any existing members not in the import source will be pushed to the beginning of the child list in their existing order. For detailed examples, see Reordering Existing Member Examples.

  6. Click Next.

    The Dimension Mapping screen is displayed. Now, define the property mapping options, as described in Dimension Mapping—Property Mapping Options.