Home > Working with Planning Projects > Building an Application > Model Flow and Linking Models

Model Flow and Linking Models
Last Updated 8/21/2008 1:17 PM

The ability to define a 'map' which enables data to flow from one model to another, within a Cascade Planning project or between projects, is a key element in the design of a modular approach. This approach lets us break the project up into modular components. For nexample we may have a Profit and Loss model, which in turn derives some of its data from a General Expenses model and some of its data from a Revenue model. Each model can have different dimensions, the only requirement being that we can specify how the data is mapped between the different models.

Cascade Planning provides two different approaches to linking data between models, and you may decide to adopt one or the other, or both, dependent on the requirements, performance considerations and design. In some cases one method may appear better suited than the other.

The first approach uses a 'push' approach, whereby the source model (the model we are linking data from), pushes the data into the target model (the model we are linking to).

The second approach uses a 'pull' or 'fetch' methodology, whereby we define an expression in the target model that fetches the data from the source model.

Using Links (the 'Push' Method)

Cross Referencing (the 'Pull' Method)