<?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: Data modeling issue in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Data-modeling-issue/m-p/747339#M266703</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Marcus,&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;Thanks for your suggestion. but.can you tell bit more about how to use MAPPING table in this case.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 07 Jan 2015 11:47:51 GMT</pubDate>
    <dc:creator>vijetas42</dc:creator>
    <dc:date>2015-01-07T11:47:51Z</dc:date>
    <item>
      <title>Data modeling issue</title>
      <link>https://community.qlik.com/t5/QlikView/Data-modeling-issue/m-p/747336#M266700</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have 5 fact tables at the time of data modeling i need to concatenate all the fact tables but some of the keys are not common in all the tables so in that case what should i do please give your suggestions on the same.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Jan 2015 11:37:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Data-modeling-issue/m-p/747336#M266700</guid>
      <dc:creator>vijetas42</dc:creator>
      <dc:date>2015-01-07T11:37:39Z</dc:date>
    </item>
    <item>
      <title>Re: Data modeling issue</title>
      <link>https://community.qlik.com/t5/QlikView/Data-modeling-issue/m-p/747337#M266701</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Post some sample data ....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Jan 2015 11:41:12 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Data-modeling-issue/m-p/747337#M266701</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2015-01-07T11:41:12Z</dc:date>
    </item>
    <item>
      <title>Re: Data modeling issue</title>
      <link>https://community.qlik.com/t5/QlikView/Data-modeling-issue/m-p/747338#M266702</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Vijeta,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this is a fairly common situation, and shouldn't really be a problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you can derive missing keys, for example by using a MAPPING table, then this is a good idea.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Otherwise just leave the missing keys as null values. This is valid also as some facts may not have any logical relationship to some of your dimensions. For example if you have Order and Invoice fact types, and Order and Invoice dimension tables it makes sense that Order facts will have a key to the Order dimension but not the Invoice dimension, and vice versa.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Marcus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Jan 2015 11:43:44 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Data-modeling-issue/m-p/747338#M266702</guid>
      <dc:creator>marcus_malinow</dc:creator>
      <dc:date>2015-01-07T11:43:44Z</dc:date>
    </item>
    <item>
      <title>Re: Data modeling issue</title>
      <link>https://community.qlik.com/t5/QlikView/Data-modeling-issue/m-p/747339#M266703</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Marcus,&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;Thanks for your suggestion. but.can you tell bit more about how to use MAPPING table in this case.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Jan 2015 11:47:51 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Data-modeling-issue/m-p/747339#M266703</guid>
      <dc:creator>vijetas42</dc:creator>
      <dc:date>2015-01-07T11:47:51Z</dc:date>
    </item>
    <item>
      <title>Re: Data modeling issue</title>
      <link>https://community.qlik.com/t5/QlikView/Data-modeling-issue/m-p/747340#M266704</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In that case you have to force concatenate the tables using &lt;STRONG&gt;Concatenate&lt;/STRONG&gt; statement. And it would be helpful if you create an additional field something like Flag to track the source of table. This flag field could be used in the set analysis in the front-end. Like:&lt;/P&gt;&lt;P&gt;Load A, B,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 'T1' as Flag&lt;/P&gt;&lt;P&gt;From T1;&lt;/P&gt;&lt;P&gt;Concatenate&lt;/P&gt;&lt;P&gt;Load A, B, C&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 'T2' as Flag&lt;/P&gt;&lt;P&gt;From T2;&lt;/P&gt;&lt;P&gt;Concatenate&lt;/P&gt;&lt;P&gt;....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Jan 2015 11:48:34 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Data-modeling-issue/m-p/747340#M266704</guid>
      <dc:creator>tresB</dc:creator>
      <dc:date>2015-01-07T11:48:34Z</dc:date>
    </item>
    <item>
      <title>Re: Data modeling issue</title>
      <link>https://community.qlik.com/t5/QlikView/Data-modeling-issue/m-p/747341#M266705</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;If this is UN-Comman fields not effecting your model then you go for concatenate this fact tables. Other way is create the joins between the Fact tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Anand&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Jan 2015 12:11:50 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Data-modeling-issue/m-p/747341#M266705</guid>
      <dc:creator>its_anandrjs</dc:creator>
      <dc:date>2015-01-07T12:11:50Z</dc:date>
    </item>
    <item>
      <title>Re: Data modeling issue</title>
      <link>https://community.qlik.com/t5/QlikView/Data-modeling-issue/m-p/747342#M266706</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Vijeta,&lt;/P&gt;&lt;P&gt;Concatenating 5 fact tables will not be an issue as long as you create a flag for each of these fact tables during concatenation, ie. `Fact1` as transactionType, `Fact2` as transactiontype and so on.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As long as these fact tables have common keys to link to their respective dimension tables, this solution should work fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Jan 2015 12:38:53 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Data-modeling-issue/m-p/747342#M266706</guid>
      <dc:creator />
      <dc:date>2015-01-07T12:38:53Z</dc:date>
    </item>
  </channel>
</rss>

