This content has been marked as final. Show 5 replies
If a dimension NODE is joined with diferent facts like F1,F2 etc no need to go with alias for NODE.
If the NODE wants to join with same fact F1 for different join conditions then you have to go alias for NODE.
As per the consistence check rpd will allows a single join between the physical layer objects, so as per the best practices we go for alias tables for each leaving original tables a side.
hope this helps
let'us suppose that NODE is a conformed dimension shared between 10 facts.
let's suppose that from RELATIONSHIP fact I want to drill down to NODE ORIGIN or NODE DESTINATION and than to the 10 facts..
I need to create and alias for all 10 fatcs for splitting the case of role ORIGIN from role DESTINATION...Is it correct?
Is there a better design approach avoiding this problem?
NODE as confirmed dimension shared among 10 facts: Assuming these 10 facts sitting in same subject area, you suppose to use Content tab to set NODE levels so that BI server pick right source(fact) based on columns select.
If helps pls mark
sorry my question was different
IF NODE is conformed among 10 facts and, cause my original question, I need to create two aliases of NODES ... this means that i need to create aliases for all 10 facts for ensuring a right drill-down or rollup
Edited by: Ric79 on Nov 21, 2012 9:38 PM
Yes,To drill or roll up based on NODE ORIGIN or NODE DESTINATION