48 Changing the Bound Viewpoint to Export an Alternate Viewpoint

This use case describes changing the viewpoint bound to a dimension so that you can export an alternate viewpoint.

Each dimension has one viewpoint that is bound to it. When you import a dimension, the objects in the viewpoint’s bound data chain are updated. When you export to a dimension, the objects in your bound viewpoint are exported.

For more information see:

• Understanding Bindings and Bound Data Objects

• Defining Alternate Views and Viewpoints

• Copying a Viewpoint

• Changing the Viewpoint Bound to a User Defined Dimension in Universal Applications

Scenario

• Our company will be adding operations in Germany next year. We need to start planning for that change.

• We have an existing Departments viewpoint. This viewpoint is bound to the Departments dimension.

• We’ll create a copy of the Departments viewpoint to use as a starting point for our Depts Next Year viewpoint.

• We’ll make changes to the Depts Next Year viewpoint – adding the new Germany parent and its children.

• When we’re ready to include the Depts Next Year viewpoint in our application, we’ll change the viewpoint that’s bound to the Departments dimension and export the dimension.

This diagram shows the data objects for the bound viewpoint and the new objects that will be created from copying the existing viewpoint and copying relationships only. We’ll reuse the same node types that are used in the copied viewpoint.

Prerequisites

This use case assumes that:

• An application has been registered.

• The Departments dimension has been imported.

• A viewpoint named Departments is bound to the Departments dimension.