Multipath Overview

When there are numerous data tables with complex associations set among them, multipath may exist between one table to another.

For example, there are two paths for you to associate table A with table C, as shown in the following figure. You can directly associate table A with table C, or you can indirectly achieve the association through table B.

Multipath includes redundant multipath and incorrect paths.

Redundant multipath: The data obtained from its associated tables through multipath are the same, but some paths are complex and some are simple. For example, table A to table C is obviously simpler than table A to table C through table B. In order to reduce FineBI server pressure, you can directly choose a simple path for data association.

Incorrect paths: Certain paths need to be deselected to ensure that the non-business-needed data are excluded from the data analysis.

Two solutions for you to optimize the multipath for a better business analysis are as follows.

Standardizing the Establishment of Data Association

To avoid the redundant multipath, you need to standardize your operations when adding tables and establishing associations.

For details, you can refer to Association Setting.

Multipath Setting Page

On the multipath setting page, paths between source tables and destination tables are displayed for you to select.

For details, you can refer to Multipath Setting Page.