Setting Linkage Between Components

Version

Application Scenarios

By setting linkages, you can click a component with the relevant data displayed in other components.

For example, if you click Offline Channel in a component, the relevant data is automatically displayed in other components. 

Note:

Linkage is the data filtering between components. For details about the results of component linkage, see Viewing Filter Criteria.

Function Introduction

Two ways to set linkages:

• Create associations for the tables used by the components. Then the system automatically set linkages between components. For details, see section "Default Linkage."

• Manually set linkages. For details, see section "Manually Setting Linkages."

Linkages can be set only between internal components within a dashboard. If you want to set linkages between dashboards, see Component Jump.

Application Scope

• Detail tables and text components can only be linked passively.

• Filter components cannot be set with linkage.

• In chart components (using no indicator fields) except for map components, linkages cannot be triggered if you click the charts.

If multiple components use the same data table, or associations exist between the used data tables in Model View, default linkages exist between these components.

Linkages are indirectly set between components after you create associations for the data tables of the subject in the model. For details, see Model View.

Note:
If associations are set in Public Data but not set in My Analysis for those tables in My Analysis using data from Public Data, no linkage is generated by default between the components made using these tables.

Example

1. This section takes Company Comprehensive Operation Dashboard, a built-in analysis subject under My Analysis, as an example.

2. Default linkages exist between the components in this subject because they share the same data table Internet Channel Statistics.

3. If Enable Default Linkage is unticked, all default linkage settings in the dashboard are removed.

Default linkages can be modified manually. For details, see section "Manually Setting Linkages."

Relationship Between Linkage and Linkage Direction

This section takes the above dashboard as an example to introduce how to set linkages manually. After Enable Default Linkage is unticked, no linkage settings exist in Company Comprehensive Operation Dashboard.

The following introduce how to manually set a bidirectional linkage between the First Class Channel Access Data component and Secondary Class Channel Access Data component.

Setting a Unidirectional Linkage from First Class Channel Access Data to Secondary Class Channel Access Data

Procedure

1. Click Set Linkage of the First Class Channel Access Data component.

2. Click the linkage icon on the Secondary Class Channel Access Data component and click OK to create a unidirectional linkage.

Dependent fields are required for creating a linkage between two components.

Notes for dependent field customization

• Field types of customized dependent fields need to be the same. If not, dependent fields are highlighted in red, indicating that linkages cannot be generated between the components.

• Dependent fields between the linked components cannot be reused.

Note:

If the data table used by the component changes (such as being replaced), all linkage-triggered dependent fields related to the component are invalid.

Effect Display

If you click First Class Channel Access Data, Secondary Class Channel Access Data changes accordingly.

If you click Secondary Class Channel Access Data, however, First Class Channel Access Data does not change. In this way, a unidirectional linkage is set.

Setting a Linkage from Secondary Class Channel Access Data to First Class Channel Access Data

Procedure

1. Set a linkage for the Secondary Class Channel Access Data component.

2. Click the linkage icon on the First Class Channel Access Data component and click OK.

In this way, the linkage from Secondary Class Channel Access Data to First Class Channel Access Data is set. Combined with the settings in section "Setting a Unidirectional Linkage from First Class Channel Access Data to Secondary Class Channel Access Data", a bidirectional linkage is set between the two components.

Effect Display

The effect of a bidirectional linkage is shown in the following figure.

If two components using two different tables need to be linked, dependent fields need to be customized.

Notes for dependent field customization

• Field types of customized dependent fields need to be the same. If not, linkages cannot be generated between the components with dependent fields highlighted in red.

• Dependent fields between the linked components cannot be reused.

Note:

If the data table used by the component changes (such as being replaced), all linkage-triggered dependent fields related to the component are invalid.

For example, the Visist Platform Pageview Distribution component and the Platform User Type Browsing Distribution component are made using two tables. To set a linkage between them, you need to click the linkage icon and then click the edition icon to add dependent fields.

• A master component can pass only one filtering condition at a time. That is to say, the linkage effects by previous triggering (in a different area within the component) will be overwritten by later triggering. For example, assume that a linkage has been triggered through indicator A in the master component. If you click indicator B of the same component, the previous linkage filtering condition (generated by clicking indicator A) is replaced.

• A slave component can receive multiple filtering conditions at a time. The filtering conditions passed from different components coexist.

• If you click a component (with two or more linkages or jumps set) is clicked, multiple prompts pop up.

If you do not want multiple prompts and just want to trigger a jump or linkage directly, ensure that the component to be clicked is set with only one linkage or jump.