Understanding cube dependency

Dependencies are established generally when a user executes a query on a cube and when that query includes a rule-calculated value from another cube. A dependency can be established to one or many cubes based on the scope of the rule within the Base cube.

Here is a simple example of a dependency within Planning Analytics:

In this simple case, the caches in Base cube are invalidated when:

• there is a change in the Base cube itself

  or

• there is a change in the dependent cube

Since a dependency is established, when there is a change in the dependent cube, the Base cube must also change.

Without this dependency map, the Base cube data could become inconsistent with the Dependent cube. The Base data is dependent upon the data in the dependent cube so any change in the Dependent cube requires the Base cache to change also.