Hi all BO Guru’s
I have a situation, based on the attachment.
right now i have 2 context
F1 TO F2 (F2 ALIAS) AND F3
CONTEXT 1: F1 TO F3
CONTECT 2: F1 TO F2 TO F3
ALL ONE TO MANY RELATIONSHIP…
PLEASE SUGGEST A HELP …
I HAVE EXPLAINED MORE BREIFLY IN ATTACHMENT…
Thanks in Advance
CONTEXT AND TRAP.doc (23.0 KB)
Sunil123 (BOB member since 2009-12-05)
Do you get the same answer going from F1 to F3 that you do going the longer route (F1 - F2 - F3)? If you do, then F1 - F3 should be a shortcut join and you don’t need contexts.
As far as attachments, they are supposed to be used for supplemental information (such as screen shots) not to provide details about the issue. People cannot search attachments, non-registered members cannot see them, and many folks won’t download attachments from unknown sources. Please keep this in mind for the future.
Dave Rathbun 
(BOB member since 2002-06-06)
Thanks You very much Dave for your Reply…
and i’ll keep in mind about attachment in future…
The values will be different from F1 to F3 context and F1 TO F2 TO F3 Context…
beacuse F2 to F3 are one to many… and F1 and F2 are one to Many…
F1 is Sales fact and F2 is Region Fact and F3 is Branch…
each region has many branches… if i use F1 dimension and F3 Measure number of count will be reduced in F1 to F2 to F3 Context…
ALL F1, F2 and F3 are comptiable… and if i drag F3 measure and F1 dimensions throws context… which user dont want…
all 3 facts are comptiable…
i want to stop context poping up…
Thanks and appreciate in Advance…
Sunil123 (BOB member since 2009-12-05)
F1 = Sales
F2 = Region
F3 = Branch
You have joined Sales to Branch
You have joined Sales to Region to Branch
You said that a Region can have many Branches. If that is the case, your joins are incorrect. It should be Region -< Branch -< Sales and then you don’t have any context issues.
Dave Rathbun (BOB member since 2002-06-06)
Thanks Dave…
Sales fact has high granularity…
which is also called head quarter sales…
HQ Sales fact to Region and Branch…
right now i stick to your previous suggestion… F1 TO F2 TO F3 AND F1 TO F3 Short cut join…
in F1 TO F2 TO F3 context should i add F1 TO F3 Short cut join…???
and my attachment has fan Trap…???(F1 -->F2 --> F3 ) ALL has dimensions and measures all are comptiable to each other…
Sunil123 (BOB member since 2009-12-05)
Shortcut joins do not need to be added to contexts.
Dave Rathbun (BOB member since 2002-06-06)
Thank you very Much…
I have 3 Fact Tables… F1 —> F2-----> F3
all have dimensions…? all are compatible to each other…
Is the above has Potential Fan Trap… Please Let me Know…?
and all 3 fact tables in same context…
Sunil123 (BOB member since 2009-12-05)
Fan traps are described in some detail and with supporting links in the Designer FAQ.
Dave Rathbun (BOB member since 2002-06-06)
Thanks Dave…
F2 measures and F3 Measures are aggregate Aware… like (sales revenue)
from both the fact table…
so when i pick dimension from F1 Table and meaure sales revenue… which is from F2 and F3 … which is directly picking from F2… what if user want to see from F3…
I cant make F2 Incomptaibale with F1… it should be comptaible…
F1 to F3 i made a short cut Join…
i want to know… how to achive F1 Dimension to F3 Aggregate measure without make incomptiable with F2 and F1…
Thanks in advance…
Sunil123 (BOB member since 2009-12-05)
Thanks a Lot Dave…
I really Appreciate…
Sunil123 (BOB member since 2009-12-05)