Author Topic: Outer joins in FW  (Read 3496 times)

Offline addicted2cognos

  • Full Member
  • ***
  • Join Date: Jan 2007
  • Posts: 15
  • Forum Citizenship: +0/-0
Outer joins in FW
« on: 11 Jan 2008 01:57:02 pm »
Anybody faced problems using outer joins in fw(trying to implement a left outer join) with an inner join to another table
« Last Edit: 11 Jan 2008 03:03:38 pm by addicted2cognos »

Offline Arpit Agrawal

  • Arpit Agrawal
  • Community Leader
  • *****
  • Join Date: Jun 2011
  • Posts: 92
  • Forum Citizenship: +6/-0
  • Have no fear of perfection--you'll never reach it.
    • Infocepts
Re: Outer joins in FW
« Reply #1 on: 14 Jun 2011 06:16:53 am »
What is the issue you are facing,In case you want to impliment a Left/Right Outer join,you can change the cardinality to 0 for the side which is deficit of the information.

Hope this helps,Let me know in case you still face any issue.

Thanks and Best regards,
Arpit Agrawal | InfoCepts |

Offline wyconian

  • Statesman
  • ******
  • Join Date: Mar 2008
  • Posts: 360
  • Forum Citizenship: +26/-0
Re: Outer joins in FW
« Reply #2 on: 21 May 2012 10:45:08 am »

Arpit answers is really good for the question you asked.  But, outer joins are bad in terms of performance and can make it harder to write reports.

Is your model based on a  datawarehouse?  If it is and you're using Data Manager as the ETL engine you can add something called a static member to the dimension builds.  This is like a default value for the 'Unknown' or 'missing' record in the dimension.  When you then come to do the surrogate key substitution on the fact table you can decide to use the static member if the real record cab't be found or is missing.  In this way you can completely remove the need for outer joins in the model, improving performance and making the reports easier to write :)