while applying complex join(Adding more than one condition expression) between two tables, have included the Join for the third table.
while i perform the integrity check, i got error on this Join.
Ex:
Table A Join with Table B
Table C Join with Table B
but we have another Join from Table A to Table C which is causing the loop
to remove the loop i have used the Complex join in Table A to Table B and include the Join for Table C in that complex join
-> If i go to create the Alias table my query is taking long time to execute
-> When applied short cut join its removing the other joins
please suggest me solution for this issue
Can i export the universe and use the universe with this error, what can be consequences for this kind of error in BO reports? how it will impact the reports
Why not leave the loop, if it’s required? Joins that span 3 tables do not work correctly, as the “extra” table does not always get included in the FROM clause.
Add a context that includes the entire set of joins, and the loop is resolved.
If the data model requires the 3-way relationship, then you need to ensure that the relationship is properly included in the universe. Having a loop is the proper way to do that.
Dave may hunt me down for this, but sometimes I use derived tables to resolve this kind of issue where some genius data modeller has put compound foreign key components in different tables. I include the first join in the derived table so that BO is forced to include this (warning: this could introduce a performance hit if you are dealing with two big tables) and then join the third table to the derived one which now includes all the fields necessary to satisfy the join.
Derived tables are an option, certainly. It would not be the first option that I would try as derived tables - especially if they’re central to the universe structure - can really mess up performance. “Can” rather than “will” as it’s not a guarantee, but the odds are probably good that they will.
What triggers a warning flag for me was this statement:
There are always exceptions. Sometimes loops are required, and Business Objects handles that just fine as long as they’re configured correctly.
(BOB member since 2006-10-10)
(BOB member since 2002-06-06)
(BOB member since 2006-10-10)
(BOB member since 2010-11-05)
(BOB member since 2002-06-06)