<?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 Applymap,Join,Keep in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Applymap-Join-Keep/m-p/1109514#M367092</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In which situations we will go for Apply map(),join,keep?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know like if we have two fields in a table then will go for apply map(), if we do use Left Join what will happen?why we only go for Apply map()?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if mapping table have duplicate values how it will works?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Performance wise Keep would be fine, how can we decide that would be fine rather than join?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As per my Knowledge&lt;/P&gt;&lt;P&gt;If we have one to one relationship between the rows then will go for Join&lt;/P&gt;&lt;P&gt;one to many and many to many will go for Keep&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please correct me if i am wrong.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in Advance..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;Venkey&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 20 Jul 2016 14:34:20 GMT</pubDate>
    <dc:creator>venkey2847</dc:creator>
    <dc:date>2016-07-20T14:34:20Z</dc:date>
    <item>
      <title>Applymap,Join,Keep</title>
      <link>https://community.qlik.com/t5/QlikView/Applymap-Join-Keep/m-p/1109514#M367092</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In which situations we will go for Apply map(),join,keep?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know like if we have two fields in a table then will go for apply map(), if we do use Left Join what will happen?why we only go for Apply map()?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if mapping table have duplicate values how it will works?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Performance wise Keep would be fine, how can we decide that would be fine rather than join?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As per my Knowledge&lt;/P&gt;&lt;P&gt;If we have one to one relationship between the rows then will go for Join&lt;/P&gt;&lt;P&gt;one to many and many to many will go for Keep&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please correct me if i am wrong.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in Advance..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;Venkey&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Jul 2016 14:34:20 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Applymap-Join-Keep/m-p/1109514#M367092</guid>
      <dc:creator>venkey2847</dc:creator>
      <dc:date>2016-07-20T14:34:20Z</dc:date>
    </item>
    <item>
      <title>Re: Applymap,Join,Keep</title>
      <link>https://community.qlik.com/t5/QlikView/Applymap-Join-Keep/m-p/1109515#M367093</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HIC wrote some useful docs on jon, keep, etc....&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/qlik-blogpost/2756"&gt;Don't join - use Applymap instead&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/qlik-blogpost/2739"&gt;To Join or not to Join&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/docs/DOC-3412"&gt;Joins and Lookups&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can also find some useful info in the Qlik help&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;H1&gt;&lt;A name="kanchor774"&gt;&lt;/A&gt;&lt;EM&gt;Keep&lt;/EM&gt;&lt;/H1&gt;&lt;P&gt;&lt;EM&gt;The &lt;SPAN class="Bold"&gt;keep&lt;/SPAN&gt; prefix is similar to the &lt;A class="MCXref_0"&gt;Join&lt;/A&gt; prefix. Just as the join prefix, it compares the loaded table with an existing named table or the last previously created data table.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;But instead of joining the loaded table with an existing table, it has the effect of reducing one or both of the two tables before they are stored in QlikView, based on the intersection of table data&lt;/STRONG&gt;. The comparison made is equivalent to a natural join made over all the common fields, i.e. the same way as in a corresponding join. However, the two tables are not joined and will be kept in QlikView as two separately named tables.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;H1&gt;&lt;EM&gt;&lt;A name="kanchor773"&gt;&lt;/A&gt;Join&lt;/EM&gt;&lt;/H1&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;The &lt;SPAN class="Bold"&gt;join&lt;/SPAN&gt; prefix joins the loaded table with an existing named table or the last previously created data table. The join is a &lt;A class="MCXref_0"&gt;Natural Join&lt;/A&gt; made over all the common &lt;/STRONG&gt;&lt;A class="MCXref_0"&gt;&lt;STRONG&gt;Fields&lt;/STRONG&gt;&lt;/A&gt;. The join prefix may be preceded by one of the prefixes &lt;A class="MCXref_0"&gt;Inner&lt;/A&gt;, &lt;A class="MCXref_0"&gt;Outer&lt;/A&gt;, &lt;A class="MCXref_0"&gt;Left&lt;/A&gt; or &lt;A class="MCXref_0"&gt;Right&lt;/A&gt;.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Or in these 2 images&lt;/P&gt;&lt;P&gt;&lt;IMG alt="join.png" class="jive-image image-1" src="https://community.qlik.com/legacyfs/online/131999_join.png" style="height: 441px; width: 620px;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="keep.jpg" class="jive-image image-2" src="https://community.qlik.com/legacyfs/online/132000_keep.jpg" style="height: 524px; width: 620px;" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Jul 2016 19:30:48 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Applymap-Join-Keep/m-p/1109515#M367093</guid>
      <dc:creator>maxgro</dc:creator>
      <dc:date>2016-07-20T19:30:48Z</dc:date>
    </item>
  </channel>
</rss>

