All Collections
ETO Results 4.3
Formatting Reports
ETO Results | Merged Dimensions and Details
ETO Results | Merged Dimensions and Details

To be used when using multiple queries and needing to relate common data points. #Results #MergedDimensions #Detail BO 4.3

Updated over a week ago

When using multiple queries or universes it is helpful to merge dimensions so that the objects from the different queries or universes can be used in the same tables within the report.

Merged dimensions create a merged object from the shared objects within the multiple queries. This object allows for "communication" between the two queries so that the objects can be used in the same table. The best fields to use for this are identifiers: Participant Site ID, Enterprise Site ID, etc. The data in these fields must match exactly in order to be merged properly.
For example: using a name field as a merged dimension is not a good idea as two or more participants could share a name.

Common examples of creating a merged dimension include:

  • Combining demographic information and TouchPoint data

  • To include Entity details when accessing Entity Cross Reference responses from TouchPoint data

  • When adding demographics or Program Enrollment to a report based on the Standard Touchpoint Universe NEW

First, you will want to identify the objects that the two queries share in common. Here are some examples.

The process of putting objects from two or more queries in the same table has two major steps:

  1. Merging the Objects

  2. Creating the detail(s)

STEP 1 - Create a Merged Dimension

In order to create a merged dimension in ETO Results, follow these steps:

  1. Open the main panel.

  2. Expand all queries that have objects needed for the merge.

3. Select objects from individual queries while holding the CTRL key.
4. Select the 3 circle icon to the right of one of the highlighted objects and select Merge.
5. The merged dimension will have now been created and will be visible in the Merged Dimensions folder in the Available Objects window.

Best practice tip: Change the name by clicking the 3 circle icon next to the merge dimension and selecting Edit Properties. This will help you easily identify the correct object when creating details or when using the merged object in a variable.

Adding an Object to an Existing Merge

If you want to add a new object to an existing Merged Dimension, follow these steps:

  1. Under the Document Objects panel, click the new object and the Merged Dimension while holding the CTRL key.

  2. Click on the 3 dot icon next to the merge, and click Add to Merge. Under the Merged Dimension, it should show the previous objects that were merged, as well as the new object.

Using Merged Dimensions

STEP 2 - Create a Detail

Details often provide a bridge between two data points with commonalities. When we merge Participant Site ID or Subject ID, we can make details for demographic information or unique TouchPoint answers.

Details are generally one-to-one ratios in that only one Demographic Value would be associated with each Participant Site ID.

In this example, we are creating a detail using a dimension that merges the Participant Enterprise ID in two queries. This will allow us to use this demographic with objects from both queries.

  1. Create a detail

  2. Associate it to the merged dimension

  3. Choose the detail you'd like to make. Typically, the detail only exists in one of the queries.

OTHER TIPS FOR MERGED DIMENSIONS

  • Results may create merged dimensions automatically for objects with the same name in different queries. This can cause issues between queries, confusing the report. To disallow a report from automatically creating Merged Dimensions:
    1. Select Document Properties in the Main Panel.
    2. Expand the Data Options category.

    3. Turn off the Auto-merge dimension.

  • If the same TouchPoint is being brought into a report from different queries, [Response ID_xx] can be used as a merged dimension. Do not use [Response ID] if two different TouchPoints are being pulled in, as this variable is only unique to each specific TouchPoint (every TouchPoint will have a Response ID_1, 2, 3, 4, etc.).

Did this answer your question?