In my situation a have a universe which has a lot of joins. All joins are set and the next step is to add some contexts. There are no loops but there are some traps (Chasm and Fan).
BO does not detect these traps so I’ll have to add the contexts manually.
This is a hell of a job.
Preparing this in excel would be fine and easier (you have the possibility of sorting all the joins and so on…). After completing this in excel you can upload the contexts up to BO. Work done.
There is an excelsheet at BOB’s downloads but …we are using BO XI.
I think this excel solution is a little bit older so if anybody has the wisdom or power to adjust this VBA Macro so that this excel-solution will work with XI R2.
I tried to connect the moderator (please read this! ) or add a post to this but i did not have not the rights to do this.
Hate universes where the contexts are not ‘detectable’…
When you have left the building nobody knows why the context is the way it is.
I know it is a hell of a job, but why don’t you set the cardinalities correct, so that BO can detect the contexts the way you want them to be:
FACT >- DIM >- DIM
or
CONTEXT >- LOOKUP >- LOOKUP
Of course all cardinalities are set but even then Chasm and Fan Traps traps are not recognized by using Detect Context. The only joins I cannot set to a cardinality are some restricting (e.g. with a @prompt function in it) joins because there is only 1 table involved.
I wished it worked this way but detecting is only working when you have loops in your universe. I don’t have loops in my universe but still I have 378 joins to put in several contexts.
Another problem is when clicking on a join in order to put this in a context BO has a problem when there are 378 joins. There is a delay because BO wants to show a join graphically at the same time so the scroll bars are beginning to shake!
You have to wait a few seconds and as the list of joins in your contexts increases, the delay time is also increasing. Doing by hand is almost impossible.
The cardinalities are to be set the way you want the contexts are to be detected. This has nothing to do with the ‘real’ cardinalities…
You can set these self-joins with a 1:1 cardinality
BTW: never use the function ‘Detect Cardinalities’. because this detects cardinality on how the joined tables are populated at a certain moment and has nothing to do with how you want the contexts are to be detected. Keep control !
Oh dear, sounds like you’ve created a bit of a mess for yourself. Can you try and ‘compartmentalise’ the universe; break the tables down into logical groupings etc and then build the contexts from that?
You might even find that the universe can then be split into different universes?
I think the first thing you should do is grab some paper and draw out your universe the way you would want it with your tables, alieses and contexts etc.
Thanks for the remarks. Splitting the universe is no option because my customer will not allow this since this universe is already in production worldwide so splitting it up, …no can do!
Secondly, modifying the cardinalities in order to trigger BO to set contexts could work. I’ll try that but I am sure I can find the solution in the update excel solution I mentionned.
The excel function resembles the other excel application found at the BOB’s downloads but this is one way traffic (BO> Excel) But this works with XI so I need a little help adjusting the VBA script. And after that other people can reuse that script!
Speak to you all later, :o
The universe has already been printed and its huge!
) or add a post to this but i did not have not the rights to do this.
(BOB member since 2006-09-06)
This has nothing to do with the ‘real’ cardinalities… 
(BOB member since 2004-01-29)