<?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 Creating a Link table or Concatenate in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Creating-a-Link-table-or-Concatenate/m-p/804332#M283983</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;I have around 4 fact tables.&lt;/P&gt;&lt;P&gt;The Fact have different granularity.&lt;/P&gt;&lt;P&gt;For eg, If we take 3 facts alone for analysis, the data in the Facts are at following levels.&lt;/P&gt;&lt;P&gt;Fact 1 : has data at date_key and Product_Key&lt;/P&gt;&lt;P&gt;Fact 2: has data at date_key, Entity_Key&lt;/P&gt;&lt;P&gt;Fact 3 : has data date Key, Entity_Key, Selling_Entity_Key&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I start creating the link table, I am getting "data inconsistency type D" which indicates RAM being used to the maximum.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I also observed that if I just use the Fact 1 and Fact 2, with a outer join populating a Key / Link table, the number of records are a Cartesian products. This is logical as we have 2 different set of level in the Fact 1 and Fact 2. I did this test for a data set of 10 rows.&lt;/P&gt;&lt;P&gt;But I understand from this, I wont be able to create the Key table using this approach as it would be a Cartesian of all the table rows.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you please guide me in using the approach to handle this kind of different Facts with just 1 -2 related fields and other unrelated key fields among the fact tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Venu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 10 Nov 2014 23:31:28 GMT</pubDate>
    <dc:creator>qlik_venu</dc:creator>
    <dc:date>2014-11-10T23:31:28Z</dc:date>
    <item>
      <title>Creating a Link table or Concatenate</title>
      <link>https://community.qlik.com/t5/QlikView/Creating-a-Link-table-or-Concatenate/m-p/804332#M283983</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;I have around 4 fact tables.&lt;/P&gt;&lt;P&gt;The Fact have different granularity.&lt;/P&gt;&lt;P&gt;For eg, If we take 3 facts alone for analysis, the data in the Facts are at following levels.&lt;/P&gt;&lt;P&gt;Fact 1 : has data at date_key and Product_Key&lt;/P&gt;&lt;P&gt;Fact 2: has data at date_key, Entity_Key&lt;/P&gt;&lt;P&gt;Fact 3 : has data date Key, Entity_Key, Selling_Entity_Key&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I start creating the link table, I am getting "data inconsistency type D" which indicates RAM being used to the maximum.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I also observed that if I just use the Fact 1 and Fact 2, with a outer join populating a Key / Link table, the number of records are a Cartesian products. This is logical as we have 2 different set of level in the Fact 1 and Fact 2. I did this test for a data set of 10 rows.&lt;/P&gt;&lt;P&gt;But I understand from this, I wont be able to create the Key table using this approach as it would be a Cartesian of all the table rows.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you please guide me in using the approach to handle this kind of different Facts with just 1 -2 related fields and other unrelated key fields among the fact tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Venu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Nov 2014 23:31:28 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Creating-a-Link-table-or-Concatenate/m-p/804332#M283983</guid>
      <dc:creator>qlik_venu</dc:creator>
      <dc:date>2014-11-10T23:31:28Z</dc:date>
    </item>
    <item>
      <title>Re: Creating a Link table or Concatenate</title>
      <link>https://community.qlik.com/t5/QlikView/Creating-a-Link-table-or-Concatenate/m-p/804333#M283984</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Try to concatenate and add DataType when you load every table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It's hard to say what would work for you, because it really depends on the business requirements.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try to share your app and explain the business requirements with examples&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Sergey&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Nov 2014 05:05:00 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Creating-a-Link-table-or-Concatenate/m-p/804333#M283984</guid>
      <dc:creator>SergeyMak</dc:creator>
      <dc:date>2014-11-11T05:05:00Z</dc:date>
    </item>
  </channel>
</rss>

