<?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: Load multiple tables with common and important field names in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Load-multiple-tables-with-common-and-important-field-names/m-p/2021540#M84322</link>
    <description>&lt;P&gt;I think you would potentially have to create 2 copies of the tblFinding table, one to connect to tblActions and one to connect to tblContractor&lt;/P&gt;
&lt;P&gt;That is the only way I can think you can avoid the loops.&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jan 2023 05:06:07 GMT</pubDate>
    <dc:creator>rachel_delany</dc:creator>
    <dc:date>2023-01-04T05:06:07Z</dc:date>
    <item>
      <title>Load multiple tables with common and important field names</title>
      <link>https://community.qlik.com/t5/App-Development/Load-multiple-tables-with-common-and-important-field-names/m-p/2021410#M84318</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;I have three tables where the relation between the fields is important but I cannot load them all as they create a synthetic key. Here is the structure:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="mansoorsheraz_0-1672766681968.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/97169i3678580DFE4362BF/image-size/medium?v=v2&amp;amp;px=400" role="button" title="mansoorsheraz_0-1672766681968.png" alt="mansoorsheraz_0-1672766681968.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;findings can have actions&lt;/P&gt;
&lt;P&gt;findings can be assigned to their own contractors&lt;/P&gt;
&lt;P&gt;actions can be assigned to their own contractors&lt;/P&gt;
&lt;P&gt;data for contractors come from one table only&lt;/P&gt;
&lt;P&gt;How to resolve this? There are so many fields in these tables, Concatenation doesn't look to be good as the script will get way too long. 200 plus fields.&lt;/P&gt;
&lt;P&gt;Any solution is appreciated.&lt;/P&gt;
&lt;P&gt;Update:&lt;/P&gt;
&lt;P&gt;I have been able to resolve the synthetic keys but now loops are coming which I am, unable to resolve:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="mansoorsheraz_0-1672776625989.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/97175i030B9CB3A8F9F656/image-size/medium?v=v2&amp;amp;px=400" role="button" title="mansoorsheraz_0-1672776625989.png" alt="mansoorsheraz_0-1672776625989.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2023 20:10:45 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Load-multiple-tables-with-common-and-important-field-names/m-p/2021410#M84318</guid>
      <dc:creator>mansoorsheraz</dc:creator>
      <dc:date>2023-01-03T20:10:45Z</dc:date>
    </item>
    <item>
      <title>Re: Load multiple tables with common and important field names</title>
      <link>https://community.qlik.com/t5/App-Development/Load-multiple-tables-with-common-and-important-field-names/m-p/2021540#M84322</link>
      <description>&lt;P&gt;I think you would potentially have to create 2 copies of the tblFinding table, one to connect to tblActions and one to connect to tblContractor&lt;/P&gt;
&lt;P&gt;That is the only way I can think you can avoid the loops.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jan 2023 05:06:07 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Load-multiple-tables-with-common-and-important-field-names/m-p/2021540#M84322</guid>
      <dc:creator>rachel_delany</dc:creator>
      <dc:date>2023-01-04T05:06:07Z</dc:date>
    </item>
  </channel>
</rss>

