<?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: Both Subfield and Link table are used in same table in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Both-Subfield-and-Link-table-are-used-in-same-table/m-p/1985001#M1221161</link>
    <description>&lt;DIV style="display: block; padding-right: 25px; filter: brightness(1);"&gt;The ideal approach would be to force concatenate the two tables just as it is. Perhaps, another way is to comment or remove the common field(s) that causes the synthetic keys and are not required in the data model. In that case, the DealerCode field may be redundant since the %link1 field appears to be the one that logically links both tables. If those synthetic keys are needed in the data model, then you would have to create your unique bit value for each distinct combination of the concatenated columns (Composite Keys).&lt;/DIV&gt;</description>
    <pubDate>Sun, 25 Sep 2022 04:29:59 GMT</pubDate>
    <dc:creator>BrunPierre</dc:creator>
    <dc:date>2022-09-25T04:29:59Z</dc:date>
    <item>
      <title>Both Subfield and Link table are used in same table</title>
      <link>https://community.qlik.com/t5/QlikView/Both-Subfield-and-Link-table-are-used-in-same-table/m-p/1984974#M1221160</link>
      <description>&lt;P&gt;Sample:&lt;/P&gt;
&lt;P&gt;LOAD &lt;BR /&gt;DealerCode as %link1,&lt;BR /&gt;PartNumber &amp;amp; PartDesc as %link2,&lt;BR /&gt;DealerCode, &lt;BR /&gt;DealerName, &lt;BR /&gt;BranchName, &lt;BR /&gt;AREAOFFICE, &lt;BR /&gt;ZONE, &lt;BR /&gt;Code, &lt;BR /&gt;Category, &lt;BR /&gt;[Main Dealer Code], &lt;BR /&gt;ChassisNo, &lt;BR /&gt;MODELCODE, &lt;BR /&gt;ModelDesc, &lt;BR /&gt;CurrentKMReading, &lt;BR /&gt;EngineHrs, &lt;BR /&gt;IsUnderSWarranty, &lt;BR /&gt;DIVISON, &lt;BR /&gt;SaleDate, &lt;BR /&gt;RoNumber, &lt;BR /&gt;ROOpeningDate, &lt;BR /&gt;[RO TIme], &lt;BR /&gt;SrvTypeDesc, &lt;BR /&gt;CustomerCode, &lt;BR /&gt;CustomerName, &lt;BR /&gt;PartNumber, &lt;BR /&gt;PartDesc, &lt;BR /&gt;Category.1, &lt;BR /&gt;Platform, &lt;BR /&gt;[landedcost/PC], &lt;BR /&gt;Qty, &lt;BR /&gt;BasicValue, &lt;BR /&gt;[Landed cost], &lt;BR /&gt;Profit, &lt;BR /&gt;[% Profit], &lt;BR /&gt;BillableType, &lt;BR /&gt;[BILABLE TYPE], &lt;BR /&gt;INVOICENO, &lt;BR /&gt;INVOICEDATE, &lt;BR /&gt;[INVOICE TIME], &lt;BR /&gt;MRP, &lt;BR /&gt;NDP, &lt;BR /&gt;sheet&lt;BR /&gt;FROM&lt;BR /&gt;[C:\Users\a2z\Downloads\Test file.xlsx]&lt;BR /&gt;(ooxml, embedded labels, table is [1.2 Parts sale &amp;amp; Profitability ]);&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Outstading:&lt;/P&gt;
&lt;P&gt;LOAD &lt;BR /&gt;&lt;BR /&gt;[Customer- CCA], &lt;BR /&gt;SubField([Customer- CCA], '-', 1) AS DealerCode,&lt;BR /&gt;DealerCode as %link1,&lt;BR /&gt;Customer, &lt;BR /&gt;Name, &lt;BR /&gt;City, &lt;BR /&gt;[Area Office], &lt;BR /&gt;State, &lt;BR /&gt;Zone, &lt;BR /&gt;Category as Category_out, &lt;BR /&gt;Remark, &lt;BR /&gt;[Credit Control Area], &lt;BR /&gt;CCA, &lt;BR /&gt;[Credit Limit], &lt;BR /&gt;Outstanding, &lt;BR /&gt;Balance, &lt;BR /&gt;[30-Mar-22], &lt;BR /&gt;[06-Apr-22], &lt;BR /&gt;[13-Apr-22], &lt;BR /&gt;[20-Apr-22], &lt;BR /&gt;[29-Apr-22], &lt;BR /&gt;RTGS, &lt;BR /&gt;[WARRANTY CREDIT]&lt;BR /&gt;//DealerCode &amp;amp; Category as Link1&lt;BR /&gt;FROM&lt;BR /&gt;[C:\Users\a2z\Downloads\Test file.xlsx]&lt;BR /&gt;(ooxml, embedded labels, table is [4.Outstading and aging Report]);&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Here two fields are matched and Systhnices keys are formed how to created link table or else another other option suggest&lt;/P&gt;</description>
      <pubDate>Sat, 24 Sep 2022 09:50:16 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Both-Subfield-and-Link-table-are-used-in-same-table/m-p/1984974#M1221160</guid>
      <dc:creator>Vishnu_murthy</dc:creator>
      <dc:date>2022-09-24T09:50:16Z</dc:date>
    </item>
    <item>
      <title>Re: Both Subfield and Link table are used in same table</title>
      <link>https://community.qlik.com/t5/QlikView/Both-Subfield-and-Link-table-are-used-in-same-table/m-p/1985001#M1221161</link>
      <description>&lt;DIV style="display: block; padding-right: 25px; filter: brightness(1);"&gt;The ideal approach would be to force concatenate the two tables just as it is. Perhaps, another way is to comment or remove the common field(s) that causes the synthetic keys and are not required in the data model. In that case, the DealerCode field may be redundant since the %link1 field appears to be the one that logically links both tables. If those synthetic keys are needed in the data model, then you would have to create your unique bit value for each distinct combination of the concatenated columns (Composite Keys).&lt;/DIV&gt;</description>
      <pubDate>Sun, 25 Sep 2022 04:29:59 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Both-Subfield-and-Link-table-are-used-in-same-table/m-p/1985001#M1221161</guid>
      <dc:creator>BrunPierre</dc:creator>
      <dc:date>2022-09-25T04:29:59Z</dc:date>
    </item>
  </channel>
</rss>

