Quantcast
Viewing all articles
Browse latest Browse all 5403

Contexts and join types in IDT: Best Practices?

I am working on my first BI4 universe, and asking myself some existential questions about context creation.

 

Coming from the pre-BI4 UNV world, I am familiar with contexts, and IDT seems to have a much more user-friendly interface for managing them. However, I was wondering if someone with some more hands-on experience with IDT could give me some advice concerning the new "neutral" joins. Is it better to always explicitly include ALL joins that are compatible with a context, or to rely on the "neutral" designation to include them? I can see where neutral joins are quite handy for universe maintenance -- no longer have to remember to add joins manually to multiple contexts when they're added to the universe! -- but I'm not sure how to use them from a best practices perspective.

 

Do you only include/exclude explicitly for joins that cause a problem between two tables?  For example, I have tables A and B, they can be reached through two different paths, I create two contexts to separate things.  Context 1 explicitly excludes the joins in one path and explicitly includes the joins in the other; context 2 does the opposite.  All other joins which are compatible with both contexts are designated "neutral". Is this the way to proceed?


Viewing all articles
Browse latest Browse all 5403

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>