If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Unique and move in categories

Started by cognos05, 29 Apr 2015 03:38:08 PM

Previous topic - Next topic

cognos05

Hi,
When should I check unique in my levels of a dimension and when to use move,

Assume I have a dimension like

Region-> Rep-> Customers

All my lowest level Customers will be unique in my datasource .

Example of data source

East -> Andrew- >1234
East- > Adam  ->2345
East->Brad->7890
East->Andrew->8765

Cube Built and Mun created for 8765 customer
Assume I have used Andrew in my report.

Now assume the customer 8765 from Andrew is moved to Adam and Andrew is resigned and no more.
so now new source data will have  East->Adam->8765.
will the existing report show error since andrew is removed ?

What will happen now , can anyone explain me.

I am not clear with Unique and Move .

Thanks,
Nithya


Rosanero4Ever

I have the same doubt...
I hope somebody can help us...

MFGF

Quote from: nithya1224 on 29 Apr 2015 03:38:08 PM
Hi,
When should I check unique in my levels of a dimension and when to use move,

Assume I have a dimension like

Region-> Rep-> Customers

All my lowest level Customers will be unique in my datasource .

Example of data source

East -> Andrew- >1234
East- > Adam  ->2345
East->Brad->7890
East->Andrew->8765

Cube Built and Mun created for 8765 customer
Assume I have used Andrew in my report.

Now assume the customer 8765 from Andrew is moved to Adam and Andrew is resigned and no more.
so now new source data will have  East->Adam->8765.
will the existing report show error since andrew is removed ?

What will happen now , can anyone explain me.

I am not clear with Unique and Move .

Thanks,
Nithya

Hi,

Unique Move takes care of re-assigning customers to new reps (in your case). If you did not use Unique Move, and customer 8675 switched in the data so that it belonged to Adam instead of Andrew, you would get a uniqueness violation in your level when attempting to build the cube, since it would see an 8675 category belonging to Andrew and an 8675 category belonging to Adam. The Unique Move option simply takes care of assigning 8675 to a new parent - Adam.

If you have used the Andrew member (category) in a report, and you do nothing to the model in Transformer, Andrew will remain in the cube, although you will not see 8675's measure values rolling up to that category. If you physically remove the Andrew category in Transformer (or do a "Clean House"), then you will end up with a report that references a non-existent member (Andrew) and your report will break.

MF. 
Meep!