Hi SCN. First post. Please be gentle!
I have created a cancatenated code and description dimension and the description has also been created as an attribute of the code's dimension parent.
I have then created a Foreign Key against the concatenated dimension and have referenced the code column, which is on the same table.
However, after checking the SQL generated by BOBJ I can see that it is still using the concatenated value in the WHERE clause instead of the code (foreign key value).
Section 10.7.4 of the IDT User Guide has the following single requirement: "Defining keys is only available for dimensions built on a data foundation."
The UNX in question meets that requirement, so I am at a loss now as to why it is not working as expected.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.