<?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 Data Model in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Data-Model/m-p/2487102#M101459</link>
    <description>&lt;P&gt;Hello everyone,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can anyone help me finding the best way to create a data model for an app. The App has 3 Fact Tables. All are now separately connected to the ClientData Table. What i need is to connect them somehow to a MasterCalendar to have a common date field in the App..&lt;/P&gt;
&lt;P&gt;These are the connections i need. But i would fall into a Loop with the following Data Model.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Anubis07_0-1728999016067.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/172959iC35DF5DEE808E1A0/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Anubis07_0-1728999016067.png" alt="Anubis07_0-1728999016067.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Does anyone has a suggestion on how should i create a data model, so that the app is smoothly running. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 15 Oct 2024 13:34:53 GMT</pubDate>
    <dc:creator>Anubis07</dc:creator>
    <dc:date>2024-10-15T13:34:53Z</dc:date>
    <item>
      <title>Data Model</title>
      <link>https://community.qlik.com/t5/App-Development/Data-Model/m-p/2487102#M101459</link>
      <description>&lt;P&gt;Hello everyone,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can anyone help me finding the best way to create a data model for an app. The App has 3 Fact Tables. All are now separately connected to the ClientData Table. What i need is to connect them somehow to a MasterCalendar to have a common date field in the App..&lt;/P&gt;
&lt;P&gt;These are the connections i need. But i would fall into a Loop with the following Data Model.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Anubis07_0-1728999016067.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/172959iC35DF5DEE808E1A0/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Anubis07_0-1728999016067.png" alt="Anubis07_0-1728999016067.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Does anyone has a suggestion on how should i create a data model, so that the app is smoothly running. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Oct 2024 13:34:53 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Data-Model/m-p/2487102#M101459</guid>
      <dc:creator>Anubis07</dc:creator>
      <dc:date>2024-10-15T13:34:53Z</dc:date>
    </item>
    <item>
      <title>Re: Data Model</title>
      <link>https://community.qlik.com/t5/App-Development/Data-Model/m-p/2487108#M101461</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A common way to resolve this when multiple fact tables are involved is to concatenate them.&lt;BR /&gt;You only need to have the same Calendar field in each table. Null value matrix are not a problem for Qlik Engine.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Kind regards&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Oct 2024 13:39:26 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Data-Model/m-p/2487108#M101461</guid>
      <dc:creator>mpc</dc:creator>
      <dc:date>2024-10-15T13:39:26Z</dc:date>
    </item>
    <item>
      <title>Re: Data Model</title>
      <link>https://community.qlik.com/t5/App-Development/Data-Model/m-p/2487334#M101513</link>
      <description>&lt;P&gt;Hi mpc,&lt;/P&gt;
&lt;P&gt;Thank you very much for the quick answer. I have thought about concatenating them by using same Periode field, but the client data cannot be always same in all 3 fact tables... and when i concatenate the tables i cannot connect it to client table based on 3 client keys..&lt;/P&gt;</description>
      <pubDate>Wed, 16 Oct 2024 11:33:59 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Data-Model/m-p/2487334#M101513</guid>
      <dc:creator>Anubis07</dc:creator>
      <dc:date>2024-10-16T11:33:59Z</dc:date>
    </item>
    <item>
      <title>Re: Data Model</title>
      <link>https://community.qlik.com/t5/App-Development/Data-Model/m-p/2487404#M101524</link>
      <description>&lt;P&gt;Within the most scenarios it's possible (and usually the simplest method) to concatenate the fact-tables - ideally by harmonizing all field-names and data-structures as much as possible.&lt;/P&gt;
&lt;P&gt;Your screenshot of the existing/intended tables looked not really suitable because it tried to connect a redundant as-of-facts with a as-of-table and on it the calendar. The facts should be rather regular and are connected with the calendar and parallele is also the as-of-table or they is then connected as satellite to the calendar.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Oct 2024 14:19:26 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Data-Model/m-p/2487404#M101524</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2024-10-16T14:19:26Z</dc:date>
    </item>
  </channel>
</rss>

