Cross Model Mapping

Cross model mapping defines how different hierarchies and member elements in two different models can be mapped to one another. This mapping allows Tabulate to enable interactions between content items from different models.


Creating Interactions

You may want to create interactions between content items (data discoveries, slicers, dynamic content, or custom formulations) that are querying different data models. For such interactions to work, the hierarchies and member elements being used as a filter must also exist in the data model of the target visualization.


If the corresponding hierarchies and member elements are identically labeled in both data models, then you can create an interaction as usual. However, if the corresponding hierarchies and/ or member elements are not identically labeled in each data model, then it's necessary to create a model mapping.

In such a scenario, the Model Mapping wizard is used to map the corresponding hierarchies and/ or member elements from the two data models, enabling the user to create interactions between them.

For instance, Model 1 may contain a date hierarchy called Date, while Model 2’s date hierarchy is called dateKey. Say that a data discovery displaying Product Sales from Model 1 is added to the presentation, along with a dateKey slicer from Model 2. When launched in runtime, Pyramid will search for the given dateKey member in the target visualization; but because Model 1 doesn't contain a hierarchy called dateKey, the user will get an error.

To enable the interaction from the dataKey slicer to the Product Sales chart, the user must configure a new model mapping which tells Pyramid that the two differently labeled hierarchies are the same.

Using the Model Mapping Wizard

To access and use the Model Mapping Wizard:

  1. Open the Model Mapping wizard from the Data area of the Advanced Settings ribbon.
  2. Click the blue plus sign (red box) in the Mapping tab to create a new model mapping.
  3. The new mapping will be listed; from the Settings panel name the mapping (blue box) and select the two models to be mapped (orange box) (the selection order is not important).
  4. The Map Hierarchies panel will open; from the drop down under each model, select the hierarchy to be mapped (yellow box).
  5. To map multiple hierarchies from the same models, click the plus sign (purple box) in the Map Hierarchies panel.
  6. From the Map Members panel, select the mapping type: either Simple or Advanced (red box).

Ignore Unmapped Hierarchies

The models being mapped may contain multiple hierarchies that are similar, yet not identical. For instance, they may both contain hierarchies listing States, where the naming convention differs between the models. In this case, if you have no need to map these hierarchies, you can simply select the 'Ignore Unmapped Hierarchies' option. This will eliminate the injection of unmapped hierarchies, preventing errors when applying interactions between visuals from the mapped models.

Mapping Types

There are 2 types of model mapping: simple and advanced. The type that you will need to configure will depend on what differences exist between the hierarchies being mapped.

Simple Mapping

If the hierarchies to be mapped are labeled differently, but each corresponding member element is identically labeled, choose Simple.

For instance, say the country hierarchy in Model 1 is called Country, while in Model 2 it's called Location. Within both hierarchies, the members are labeled identically. In this case, choose Simple and select the hierarchy name type (either Unique Name or Caption).

Model 1 Model 2
Country Location
Australia Australia
United States United States
Canada Canada
France France
Germany Germany

Advanced Mapping

Advanced Mapping is required to map the member elements within two hierarchies, if the member elements are not identically labeled. In this case, the Advanced option must be selected in order to configure the dynamic functions required to map the differently labeled hierarchy members.

Click here to review the advanced mapping functions; for a detailed examples of advanced mapping for date hierarchies, review the MemberCaption function.


Model 1 Model 2
Country Location
Australia AUS
United States USA
Canada CAN
United Kingdom UK
France FRA