<?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: Left Join (1 to Many Relationship) in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Left-Join-1-to-Many-Relationship/m-p/1583697#M42673</link>
    <description>&lt;P&gt;The simplest solution is to not join the tables and just let Qlik associate them through the common field name.&amp;nbsp; Assuming sales is in Table A it will sum correctly. A simple UI table with Sum(Sales) and Field B as the dimension will show the Sum(Sales) amount correctly per row but potentially misleading to users as the sum of the rows may not equal the overall total.&amp;nbsp;This is because a given sales amount may be associated with more than one row.&lt;/P&gt;&lt;P&gt;The best solution really depends on the nature of the data and the underlying business logic that is appropriate.&lt;/P&gt;</description>
    <pubDate>Thu, 23 May 2019 06:45:19 GMT</pubDate>
    <dc:creator>rogerpegler</dc:creator>
    <dc:date>2019-05-23T06:45:19Z</dc:date>
    <item>
      <title>Left Join (1 to Many Relationship)</title>
      <link>https://community.qlik.com/t5/App-Development/Left-Join-1-to-Many-Relationship/m-p/1583642#M42666</link>
      <description>&lt;P&gt;I have&amp;nbsp; the below script&lt;/P&gt;&lt;P&gt;Table A&lt;/P&gt;&lt;P&gt;FIeld A&lt;/P&gt;&lt;P&gt;Left Join (Table A)&lt;/P&gt;&lt;P&gt;Field A&amp;nbsp;&lt;/P&gt;&lt;P&gt;Field B&lt;/P&gt;&lt;P&gt;Field B can have multiple values for each value in Field B&lt;/P&gt;&lt;P&gt;When I am doing a table with Sum(Sales) and add Field B to the table the Sales amount will be doubled or tripled as the case may be.&lt;/P&gt;&lt;P&gt;How can I correctly show Field B without duplicating the sum sales&lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2019 00:17:32 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Left-Join-1-to-Many-Relationship/m-p/1583642#M42666</guid>
      <dc:creator>Rehan</dc:creator>
      <dc:date>2019-05-23T00:17:32Z</dc:date>
    </item>
    <item>
      <title>Re: Left Join (1 to Many Relationship)</title>
      <link>https://community.qlik.com/t5/App-Development/Left-Join-1-to-Many-Relationship/m-p/1583643#M42667</link>
      <description>&lt;P&gt;Ignore the other one . Please use this one&lt;/P&gt;&lt;P&gt;I have&amp;nbsp; the below script&lt;/P&gt;&lt;P&gt;Table A&lt;/P&gt;&lt;P&gt;FIeld A&lt;/P&gt;&lt;P&gt;Left Join (Table A)&lt;/P&gt;&lt;P&gt;Field A&amp;nbsp;&lt;/P&gt;&lt;P&gt;Field B&lt;/P&gt;&lt;P&gt;Field B can have multiple values for each value in Field A&lt;/P&gt;&lt;P&gt;When I am doing a table with Sum(Sales) and add Field B to the table the Sales amount will be doubled or tripled as the case may be.&lt;/P&gt;&lt;P&gt;How can I correctly show Field B without duplicating the sum sales&lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2019 00:19:18 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Left-Join-1-to-Many-Relationship/m-p/1583643#M42667</guid>
      <dc:creator>Rehan</dc:creator>
      <dc:date>2019-05-23T00:19:18Z</dc:date>
    </item>
    <item>
      <title>Re: Left Join (1 to Many Relationship)</title>
      <link>https://community.qlik.com/t5/App-Development/Left-Join-1-to-Many-Relationship/m-p/1583697#M42673</link>
      <description>&lt;P&gt;The simplest solution is to not join the tables and just let Qlik associate them through the common field name.&amp;nbsp; Assuming sales is in Table A it will sum correctly. A simple UI table with Sum(Sales) and Field B as the dimension will show the Sum(Sales) amount correctly per row but potentially misleading to users as the sum of the rows may not equal the overall total.&amp;nbsp;This is because a given sales amount may be associated with more than one row.&lt;/P&gt;&lt;P&gt;The best solution really depends on the nature of the data and the underlying business logic that is appropriate.&lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2019 06:45:19 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Left-Join-1-to-Many-Relationship/m-p/1583697#M42673</guid>
      <dc:creator>rogerpegler</dc:creator>
      <dc:date>2019-05-23T06:45:19Z</dc:date>
    </item>
    <item>
      <title>Re: Left Join (1 to Many Relationship)</title>
      <link>https://community.qlik.com/t5/App-Development/Left-Join-1-to-Many-Relationship/m-p/1583703#M42675</link>
      <description>&lt;P&gt;Hi Rehan,&lt;BR /&gt;&amp;nbsp;When you have one to many relation then join is behaving exactly as it supposed to do. so In qlik there are two option to cater this issue.&lt;BR /&gt;1. Instead of using join just associate both table on key fields&lt;/P&gt;&lt;P&gt;2. Use Mapping load and ApplyMap() instead of using join it will get the first value of B field against A field available in the table.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2019 07:15:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Left-Join-1-to-Many-Relationship/m-p/1583703#M42675</guid>
      <dc:creator>shair_abbas</dc:creator>
      <dc:date>2019-05-23T07:15:31Z</dc:date>
    </item>
    <item>
      <title>Re: Left Join (1 to Many Relationship)</title>
      <link>https://community.qlik.com/t5/App-Development/Left-Join-1-to-Many-Relationship/m-p/2068401#M87631</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/50001"&gt;@shair_abbas&lt;/a&gt;&amp;nbsp;could you please elaborate on your 2nd suggestion with an example? I think I may be looking for a solution like this. Thank you!&lt;/P&gt;</description>
      <pubDate>Sat, 06 May 2023 19:44:05 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Left-Join-1-to-Many-Relationship/m-p/2068401#M87631</guid>
      <dc:creator>ioannaiogr</dc:creator>
      <dc:date>2023-05-06T19:44:05Z</dc:date>
    </item>
  </channel>
</rss>

