title: MicroStrategy dimension tables left outer join fact tables scenario
body: <p>I am trying to mimic following SQL in MicroStrategy using given tables</p>
  
  <ul>
  <li><p>master_dimension - Itemkey, color, weight, season, target_age_group...   1000 rows with 1000 unique items</p></li>
  <li><p>sub_dimension - item_key, need_special_handling - 400 rows with only 400 of 1000 items having rows in this table</p></li>
  <li><p>prices - item_key, price, start_date, end_date - 600 rows with 200 unique products having price/price changes</p></li>
  <li><p>stock - item_key, available_stock_qty - 155 rows with 155 unique products having stock quantity</p></li>
  </ul>
  
  <blockquote>
  <pre><code>select            
  m.itemkey, m.color, m.weight,...
  sub.need_special_handling
  , count(p.price)
  , sum(st.available_stock_qty)
  from master_dimension  m
  left outer join sub_dimension  sub
  on m.itemkey = sub.item_key
  left outer join prices  p
  on p.itemkey = m.itemkey
  left outer join stock st
  on st.itemkey = m.itemkey
  group by
  m.itemkey, m.color, m.weight,...
  sub.need_special_handling
  </code></pre>
  </blockquote>
  
  <p>I created the attribute itemkey with all the tables involved as lookups with primary lookup table as master_dimension. I modified VLDB properties of itemkey attribute to joins->preserve all final pass result elements -> 3rd option (preserve all elements of final pass... but not relation table).
  I modified report VLDB properties to joins-> preserve all lookup table elements -> 4th option (preserve lookup elements... with filter). I played with multiple options of VLDB properties, but not able to achieve left outer join between attributes and between attribute and fact tables.</p>