<?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 Re: Strange Join considering Occurrence in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Strange-Join-considering-Occurrence/m-p/119374#M8299</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm sorry, but isn't your FinalTable exactly the same as your Tab2 ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you need a more precise association because of other fields available, then you'd need to finetune your Key. e.g. concatenate with another variable that distinguishes between 2/10 and 3/10. Could be delivery address, delivery name, date&amp;amp;hour, ....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 24 Aug 2018 10:12:36 GMT</pubDate>
    <dc:creator>puttemans</dc:creator>
    <dc:date>2018-08-24T10:12:36Z</dc:date>
    <item>
      <title>Strange Join considering Occurrence</title>
      <link>https://community.qlik.com/t5/App-Development/Strange-Join-considering-Occurrence/m-p/119372#M8297</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Today i have to face a little bit strange situation...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have these two tables:&lt;/P&gt;&lt;P&gt;Tab1:&lt;/P&gt;&lt;TABLE border="1" class="jiveBorder" height="195" style="border: 1px solid #000000; width: 72px; height: 197px;" width="70"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TH style="text-align: center; background-color: #6690bc; color: #ffffff; padding: 2px;" valign="middle"&gt;&lt;STRONG&gt;Qty (Key)&lt;/STRONG&gt;&lt;/TH&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD style="padding: 2px; text-align: center;"&gt;20&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD style="padding: 2px; text-align: center;"&gt;20&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD style="padding: 2px; text-align: center;"&gt;10&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD style="padding: 2px; text-align: center;"&gt;30&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD style="padding: 2px; text-align: center;"&gt;10&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD style="padding: 2px; text-align: center;"&gt;30&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tab2:&lt;/P&gt;&lt;TABLE border="1" class="jiveBorder" height="149" style="border: 1px solid rgb(0, 0, 0); width: 138px; height: 143px;"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TH style="text-align: center; background-color: #6690bc; color: #ffffff; padding: 2px;" valign="middle"&gt;&lt;STRONG&gt;Delivery&lt;/STRONG&gt;&lt;/TH&gt;&lt;TH style="text-align: center; background-color: #6690bc; color: #ffffff; padding: 2px;" valign="middle"&gt;&lt;STRONG&gt;Qty (Key)&lt;/STRONG&gt;&lt;/TH&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD style="padding: 2px;"&gt;1&lt;/TD&gt;&lt;TD style="padding: 2px;"&gt;30&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD style="padding: 2px;"&gt;2&lt;/TD&gt;&lt;TD style="padding: 2px;"&gt;10&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD style="padding: 2px;"&gt;3&lt;/TD&gt;&lt;TD style="padding: 2px;"&gt;10&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD style="padding: 2px;"&gt;4&lt;/TD&gt;&lt;TD style="padding: 2px;"&gt;20&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD style="padding: 2px;"&gt;5&lt;/TD&gt;&lt;TD style="padding: 2px;"&gt;30&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;6&lt;/TD&gt;&lt;TD&gt;20&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Qty&lt;/STRONG&gt; field is the key field between these tables.&lt;/P&gt;&lt;P&gt;I want to associate the first occurence of Tab2.Qty with the first occurence of Tab1.Qty, the second occurrence of Tab2.Qty with the second occurrence of Tab1.Qty... and so on, respecting the original sort order fo Tab2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So the association would be:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="2018-08-24 11_36_24-Immagine - Paint.png" class="jive-image image-1" src="/legacyfs/online/211721_2018-08-24 11_36_24-Immagine - Paint.png" style="height: auto;" /&gt;&lt;/P&gt;&lt;P&gt;In order to obtain this result:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FinalTable:&lt;/P&gt;&lt;TABLE border="1" class="jiveBorder" height="174" style="border: 1px solid rgb(0, 0, 0); width: 136px; height: 121px;"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TH style="text-align: center; background-color: #6690bc; color: #ffffff; padding: 2px;" valign="middle"&gt;&lt;STRONG&gt;Qty&lt;/STRONG&gt;&lt;/TH&gt;&lt;TH style="text-align: center; background-color: #6690bc; color: #ffffff; padding: 2px;" valign="middle"&gt;&lt;STRONG&gt;Delivery&lt;/STRONG&gt;&lt;/TH&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD style="padding: 2px;"&gt;20&lt;/TD&gt;&lt;TD style="padding: 2px;"&gt;4&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD style="padding: 2px;"&gt;20&lt;/TD&gt;&lt;TD style="padding: 2px;"&gt;6&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD style="padding: 2px;"&gt;10&lt;/TD&gt;&lt;TD style="padding: 2px;"&gt;2&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD style="padding: 2px;"&gt;30&lt;/TD&gt;&lt;TD style="padding: 2px;"&gt;1&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD style="padding: 2px;"&gt;10&lt;/TD&gt;&lt;TD style="padding: 2px;"&gt;3&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD style="padding: 2px;"&gt;30&lt;/TD&gt;&lt;TD style="padding: 2px;"&gt;5&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How to do this ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Aug 2018 09:45:02 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Strange-Join-considering-Occurrence/m-p/119372#M8297</guid>
      <dc:creator>micheledenardi</dc:creator>
      <dc:date>2018-08-24T09:45:02Z</dc:date>
    </item>
    <item>
      <title>Re: Strange Join considering Occurrence</title>
      <link>https://community.qlik.com/t5/App-Development/Strange-Join-considering-Occurrence/m-p/119373#M8298</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Key column should not have duplicates. Try to identify any column, which help you to identify each row uniquely.&lt;/P&gt;&lt;P&gt;else try to generate your own unique key to perform join.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Aug 2018 10:08:23 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Strange-Join-considering-Occurrence/m-p/119373#M8298</guid>
      <dc:creator>dsharmaqv</dc:creator>
      <dc:date>2018-08-24T10:08:23Z</dc:date>
    </item>
    <item>
      <title>Re: Strange Join considering Occurrence</title>
      <link>https://community.qlik.com/t5/App-Development/Strange-Join-considering-Occurrence/m-p/119374#M8299</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm sorry, but isn't your FinalTable exactly the same as your Tab2 ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you need a more precise association because of other fields available, then you'd need to finetune your Key. e.g. concatenate with another variable that distinguishes between 2/10 and 3/10. Could be delivery address, delivery name, date&amp;amp;hour, ....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Aug 2018 10:12:36 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Strange-Join-considering-Occurrence/m-p/119374#M8299</guid>
      <dc:creator>puttemans</dc:creator>
      <dc:date>2018-08-24T10:12:36Z</dc:date>
    </item>
  </channel>
</rss>

