<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic LEFT JOIN in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/LEFT-JOIN/m-p/279893#M1182989</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;mrkachhia,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't believe there's a way to do that using a join (at least if you use only the shown fields).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The important thing would be to know how you handle this in your business, i.e. how do you decide in your real business which record of your purchase table belongs to which customer. Then it might be possible to tell QV what to do (Maybe by adding a new field to both tables indicating an order of records, if fields used to join have the same values for multiple records, but are not really duplicates for all fields).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Stefan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 27 Oct 2011 16:08:37 GMT</pubDate>
    <dc:creator>swuehl</dc:creator>
    <dc:date>2011-10-27T16:08:37Z</dc:date>
    <item>
      <title>LEFT JOIN</title>
      <link>https://community.qlik.com/t5/QlikView/LEFT-JOIN/m-p/279892#M1182988</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have below two tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;TABLE border="0" cellpadding="0" cellspacing="0" width="402"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD class="xl70" height="21" width="159"&gt;Purchase Order Number&lt;/TD&gt;&lt;TD class="xl71" style="border-left: medium none;" width="75"&gt;Supplier ID&lt;/TD&gt;&lt;TD class="xl71" style="border-left: medium none;" width="29"&gt;Qty&lt;/TD&gt;&lt;TD class="xl71" style="border-left: medium none;" width="63"&gt;Part NO&lt;/TD&gt;&lt;TD class="xl71" style="border-left: medium none;" width="38"&gt;Price&lt;/TD&gt;&lt;TD class="xl72" style="border-left: medium none;" width="38"&gt;Total&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD class="xl67" height="20"&gt;101520&lt;/TD&gt;&lt;TD class="xl68" style="border-left: medium none;"&gt;SUP001&lt;/TD&gt;&lt;TD class="xl68" style="border-left: medium none;"&gt;25&lt;/TD&gt;&lt;TD class="xl68" style="border-left: medium none;"&gt;PART 001&lt;/TD&gt;&lt;TD class="xl68" style="border-left: medium none;"&gt;20&lt;/TD&gt;&lt;TD class="xl69" style="border-left: medium none;"&gt;500&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD class="xl64" height="21" style="border-top: medium none;"&gt;101520&lt;/TD&gt;&lt;TD class="xl65" style="border-left: medium none; border-top: medium none;"&gt;SUP001&lt;/TD&gt;&lt;TD class="xl65" style="border-left: medium none; border-top: medium none;"&gt;25&lt;/TD&gt;&lt;TD class="xl65" style="border-left: medium none; border-top: medium none;"&gt;PART 001&lt;/TD&gt;&lt;TD class="xl65" style="border-left: medium none; border-top: medium none;"&gt;20&lt;/TD&gt;&lt;TD class="xl66" style="border-left: medium none; border-top: medium none;"&gt;500&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;TABLE border="0" cellpadding="0" cellspacing="0" width="304"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD class="xl72" height="21" width="78"&gt;Sales Order&lt;/TD&gt;&lt;TD class="xl73" style="border-left: medium none;" width="83"&gt;Customer ID&lt;/TD&gt;&lt;TD class="xl73" style="border-left: medium none;" width="49"&gt;PO NO&lt;/TD&gt;&lt;TD class="xl73" style="border-left: medium none;" width="31"&gt;QTY&lt;/TD&gt;&lt;TD class="xl74" style="border-left: medium none;" width="63"&gt;Part NO&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD class="xl69" height="20"&gt;5010&lt;/TD&gt;&lt;TD class="xl70" style="border-left: medium none;"&gt;Cust 001&lt;/TD&gt;&lt;TD class="xl70" style="border-left: medium none;"&gt;101520&lt;/TD&gt;&lt;TD class="xl70" style="border-left: medium none;"&gt;25&lt;/TD&gt;&lt;TD class="xl71" style="border-left: medium none;"&gt;PART 001&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD class="xl66" height="21" style="border-top: medium none;"&gt;5011&lt;/TD&gt;&lt;TD class="xl67" style="border-left: medium none; border-top: medium none;"&gt;Cust 002&lt;/TD&gt;&lt;TD class="xl67" style="border-left: medium none; border-top: medium none;"&gt;101520&lt;/TD&gt;&lt;TD class="xl67" style="border-left: medium none; border-top: medium none;"&gt;25&lt;/TD&gt;&lt;TD class="xl68" style="border-left: medium none; border-top: medium none;"&gt;PART 001&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;Table 1 is having purchase data while table two is having sales data.&lt;/P&gt;&lt;P&gt;Both table have many other columns but don't required in this question so I have ignored them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1st table is linked with 2nd table with Left Join.&lt;/P&gt;&lt;P&gt;Both tables have more than 10000 lines. Just two lines are shown for which I have problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Question is.... I need Customer ID against my purchase table data. But due to Purchase Order Number, SUPPLIER ID, PART NUMBER and QTY all are same, chart/table in QlikView is confused which line is for which customer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any function/method, so that both lines are giving different customer ID?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Oct 2011 15:22:24 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/LEFT-JOIN/m-p/279892#M1182988</guid>
      <dc:creator />
      <dc:date>2011-10-27T15:22:24Z</dc:date>
    </item>
    <item>
      <title>LEFT JOIN</title>
      <link>https://community.qlik.com/t5/QlikView/LEFT-JOIN/m-p/279893#M1182989</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;mrkachhia,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't believe there's a way to do that using a join (at least if you use only the shown fields).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The important thing would be to know how you handle this in your business, i.e. how do you decide in your real business which record of your purchase table belongs to which customer. Then it might be possible to tell QV what to do (Maybe by adding a new field to both tables indicating an order of records, if fields used to join have the same values for multiple records, but are not really duplicates for all fields).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Stefan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Oct 2011 16:08:37 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/LEFT-JOIN/m-p/279893#M1182989</guid>
      <dc:creator>swuehl</dc:creator>
      <dc:date>2011-10-27T16:08:37Z</dc:date>
    </item>
    <item>
      <title>LEFT JOIN</title>
      <link>https://community.qlik.com/t5/QlikView/LEFT-JOIN/m-p/279894#M1182990</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; I think that you must have a unique field that may differentiate between the two tables.You must ask with the business user ,because qlikview will not be able to differentiate&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Oct 2011 04:21:44 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/LEFT-JOIN/m-p/279894#M1182990</guid>
      <dc:creator>kamalqlik</dc:creator>
      <dc:date>2011-10-28T04:21:44Z</dc:date>
    </item>
  </channel>
</rss>

