PowerPlay Transformer

[JackONeill]

Someone can tell me

How to associate columns in the data source to
higher levels in the dimensions.

here is the problem

I have two database
first:
Name, Status

Second
Name,divisions,product,sales


i d like to made a dimension

Status
Divisions
name


but i can't use the uniqueness option...

The program tell me to associate columns in the data source to a higher levels in the dimensions???

What is the problem???

CU

 

[cstarpdx]

Don't think you will be able to do this. With multiple datasources, you will need to identify the lowest field as unique. If the name field by itself cannot be unique, then I would create a calculated column that concatenates division + name, use this new calculated column as the field source, and the name field, as the field label.

This still will not allow you to have status before division, as name is the lowest level, and there is not enough information to show a relationship between name,division,status.

If you can put status in the 2nd datasource, or division in the 1st, then you can probably make it work, but otherwise, you are probably out of luck to make this drill down path work.

Regards,
Jim

 

[JackONeill]

Thank for the answer!

Of Course Name should be set as unique !

but when i do this he tell me that for a custumer

he has already create a dimension and the program stop!
this should be normal

in my ex:

Status/division/name
IN / DIVA / Alpha
IN / DIVB / Alpha

this should be ok because in my alpha (name) can be in both DIVA and DIVB...

the same

OUT / DIVA / Alpha
OUT / DIVB / Alpha


So as all the name can be in the lowest level of the dimensions i can't set it up as unique...

Do you have a solution???

I will try your concatenate solution...

 

[cstarpdx]

Based on your example, name is not unique.

IN / DIVA / Alpha
IN / DIVB / Alpha
OUT / DIVA / Alpha
OUT / DIVB / Alpha

Alpha shows up 4 times under different drill down paths. For Transformer to work you will need to have all of the fields in a single query, or some way of showing the following as the source values.

IN / IN-DIVA / IN-DIVA-Alpha
IN / IN-DIVB / IN-DIVB-Alpha
OUT / OUT-DIVA / OUT-DIVA-Alpha
OUT / OUT-DIVB / OUT-DIVB-Alpha

There is also the question of how to handle movement of Alpha if you choose. If Alpha started in DIVA, then moved to DIVB, do you want Alpha data to show some in DIVA and DIVB, or all Alpha data to show in DIVB? If all Alpha data should show in DIVB then you should set the name field to unique/move.

The same holds true for Status. If Alpha was status IN and is now status OUT, where should Alpha data reside?

These questions need to be answered before you start to
concatenate fields, otherwise you will create a different problem.