Move Categories When Source Data Changes - IBM Cognos User Manual

Tip: Click Refresh Source to refresh the source list for the data source. Click
Validate to check whether columns in the model violate any Framework
Manager governor settings.
4. For columns that you want to remove from the model, select the columns in
the model list and click Remove.
5. For unmatched columns identified by and X in the Matched to Source column
in the model list, do one of the following:
v To manually match query items to columns, select a data source item in the
Source list and a column in the model, and click Match.
v To allow Cognos Transformer to automatically match query items to
columns, select the columns in the model and click Auto Match.
6. If Cognos Transformer provides one or more locations in the data source that
may be appropriate for unmatched columns, do one of the following:
v If one of the locations is an appropriate match, select the location and click
Next or Finish.
v If none of the locations are an appropriate match, click Match by reference
instead and click Next. From the Candidates list of data source items, click
the one that you want to match to the column or click Leave unmatched.
7. Repeat step 6 for each mismatched column that Cognos Transformer attempts
to resolve.
8. For any mismatched items that Cognos Transformer cannot suggest locations
for, Cognos Transformer presents possible name changes for your review. From
the Candidates list, click the item that you want to match to the column to or
click Leave unmatched.
Results
Data source items are now synchronized with the model.

Move Categories When Source Data Changes

You can prevent model errors due to changes in your source by designating a
unique level. This tells Cognos Transformer that categories in that level are
identified by their source values alone, without reference to their ancestors.
However, when you move a category within a unique level, a uniqueness violation
is reported during category generation because the moved category now appears
in a different context.
To avoid having to manually restructure the categories in a unique level to
conform to the changed ancestor data, you can specify that such changes be treated
as unique moves. Measure values are thereafter rolled up the new path from the
moved categories.
If any cube in the model is set to incrementally update, you cannot specify changes
as unique moves. Conversely, if unique moves are specified for any level, you
cannot set incremental updates for the cubes.
Unique move is supported for time-based partitioned cubes. In the member cubes
that were created before the category was moved, the category will remain
connected to the previous parent and values will roll up to that parent. In member
cubes that were created after the category was moved, the category will be
connected to the new parent and values will roll up to the new parent.
Chapter 8. PowerCubes in Production Environments
173