<?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: ApplyMap in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/ApplyMap/m-p/105036#M766347</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Avoid using join as far as possible and use applymap instead, even where several applymap are required. &lt;/P&gt;&lt;P&gt;Missing records can be given a name. Like 'Missing' . Or can be used to group records. So an excel spreadsheet will have the Focus Customers and the rest will be grouped as 'Other&lt;/P&gt;&lt;P&gt;In single mapping, performance is almost the same for both methods. But if there are a lot of fields to map in one table, better are ApplyMap functions. Datamodel decreased after reload.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Joins may cause data to be inadvertently duplicated and can be slow during reloads.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Left/Right join" both tables affected on record level - number of records of left/right table may grow and/or double records both tables may be withdraw. Datamodel get complexity.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ApplyMap do not affects records at all.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 03 Jul 2018 17:33:05 GMT</pubDate>
    <dc:creator>BalaBhaskar_Qlik</dc:creator>
    <dc:date>2018-07-03T17:33:05Z</dc:date>
    <item>
      <title>ApplyMap</title>
      <link>https://community.qlik.com/t5/QlikView/ApplyMap/m-p/105033#M766344</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Difference between ApplyMap and Join.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How applymap work internally in qlikview.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Villyee.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Nov 2020 16:16:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/ApplyMap/m-p/105033#M766344</guid>
      <dc:creator>vanderson009</dc:creator>
      <dc:date>2020-11-25T16:16:04Z</dc:date>
    </item>
    <item>
      <title>Re: ApplyMap</title>
      <link>https://community.qlik.com/t5/QlikView/ApplyMap/m-p/105034#M766345</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A join is a merging of tables in regard to the specified key-fields, the used join-type (left, right, inner, outer) and the values within the key-fields (how they relate to eachother - 1:1, 1:n, n:n - and/or if there are missing ones). It's a complex process and could require large amounts of resources, especially RAM and time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A mapping with applymap() is instead a kind of a lookup - quite similar to the Excel function lookup() - which is used to add, replace or filter values within a table. It's much simpler and faster as a join and there is no risks to change the number of records unintentionally.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also see: &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;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Jul 2018 12:20:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/ApplyMap/m-p/105034#M766345</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2018-07-03T12:20:22Z</dc:date>
    </item>
    <item>
      <title>Re: ApplyMap</title>
      <link>https://community.qlik.com/t5/QlikView/ApplyMap/m-p/105035#M766346</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; please refer Below link that may helpful for you&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.qlik.com/servlet/JiveServlet/previewBody/3412-102-4-3894/Joins and Lookups.pdf" title="https://community.qlik.com/servlet/JiveServlet/previewBody/3412-102-4-3894/Joins%20and%20Lookups.pdf"&gt;https://community.qlik.com/servlet/JiveServlet/previewBody/3412-102-4-3894/Joins%20and%20Lookups.pdf&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Jul 2018 12:59:56 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/ApplyMap/m-p/105035#M766346</guid>
      <dc:creator>sujan24s</dc:creator>
      <dc:date>2018-07-03T12:59:56Z</dc:date>
    </item>
    <item>
      <title>Re: ApplyMap</title>
      <link>https://community.qlik.com/t5/QlikView/ApplyMap/m-p/105036#M766347</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Avoid using join as far as possible and use applymap instead, even where several applymap are required. &lt;/P&gt;&lt;P&gt;Missing records can be given a name. Like 'Missing' . Or can be used to group records. So an excel spreadsheet will have the Focus Customers and the rest will be grouped as 'Other&lt;/P&gt;&lt;P&gt;In single mapping, performance is almost the same for both methods. But if there are a lot of fields to map in one table, better are ApplyMap functions. Datamodel decreased after reload.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Joins may cause data to be inadvertently duplicated and can be slow during reloads.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Left/Right join" both tables affected on record level - number of records of left/right table may grow and/or double records both tables may be withdraw. Datamodel get complexity.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ApplyMap do not affects records at all.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Jul 2018 17:33:05 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/ApplyMap/m-p/105036#M766347</guid>
      <dc:creator>BalaBhaskar_Qlik</dc:creator>
      <dc:date>2018-07-03T17:33:05Z</dc:date>
    </item>
  </channel>
</rss>

