Common mistakes in BOARD relationship model

Document created by ggallo Employee on Jul 13, 2017
Version 1Show Document
  • View in full screen mode

1. Indirect Relationship Missing

In a BOARD database, relationships define an n-to-1 (or 1-to-1) connection between elements of the more granular entity to the more aggregated one. These entities would be referred to as the "child" (more granular) and the "parent" (more aggregated) entity.

 

A direct relationship is a one-level "child" > "parent" relationship.

For example Customer > City could be a direct relationship, having City connected directly to Customer as the entity one level above.

An indirect relationship is a "child" > "grand parent" relationship

For example Customer > City > Region could be a tree, where Region is "grand parent" of Customer.

 

During the creation of relationships, both direct and indirect relationships must be defined.

 

In the above example Customer > Region is an indirect relationship which could be derived from Customer > City & City > Region

Sometimes, with complex hierarchies, it is possible to miss some of the indirect relationships.

 

Indirect relationship missing between Customer and Region > Effect on the Layouts:

 

Adding an Infocube to a layout which is structured by Customer, the aggregated entity missing indirect relationship (Region), is not available in the Axes definition tab.

 

Indirect relationship missing between Customer and Region > Effect on the Selections:

 

If you select a Customer (or a City), BOARD is not able to retrieve the Region to which the Customers belong to. On the other hand the selection by Region works fine.

 

 

 

2. Ring Structure Tree 

Defining cycles/rings in hierarchies is logically possible but never recommended. 

 

The normalization of Ring Structure Hierarchies is not reliable.

 

Let’s pretend that, using the following example, the "Customer A" belongs to the "City A" and to the "Region A".

The Salesperson related to "Customer A" is the "Salesperson X", who is related to the "Region B".

 

 

 

 

Indirect relationship missing between Customer and Region > Effect on the Layouts/Solution:

 

When representing information by Customer > City > Region, "Customer A" will be shown under (or belonging) to the "Region A"

 

Indirect relationship missing between Customer and Region > Effect on the Layouts/Solution:

 

When representing information by Customer > Salesman > Region, "Customer A" will be shown under (or belonging) to the "Region B"

 

3. Multiple Feet Tree

A BOARD hierarchy can only allow for one (and one only) single most granular element as the basis of a tree. Multiple "feet" hierarchies are not admitted nor supported

8 people found this helpful

Attachments

    Outcomes