<?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: Datamodel in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Datamodel/m-p/1656698#M730242</link>
    <description>&lt;P&gt;Link table may work but synthetic key s are effectively link tables that qlik creates automatically.&lt;/P&gt;&lt;P&gt;I dont know if there will be any performance benefits using link tables. You will need to try and see.&lt;/P&gt;&lt;P&gt;synthetic key (simple ones) it self does cause performance issues but looking at the data model it points to a data modelling issue. maybe you need to combine a few of the tables together.&lt;/P&gt;&lt;P&gt;to put simply there is no easy answer.&lt;/P&gt;</description>
    <pubDate>Wed, 11 Dec 2019 17:28:24 GMT</pubDate>
    <dc:creator>dplr-rn</dc:creator>
    <dc:date>2019-12-11T17:28:24Z</dc:date>
    <item>
      <title>Datamodel</title>
      <link>https://community.qlik.com/t5/QlikView/Datamodel/m-p/1656691#M730241</link>
      <description>&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;Here is my datamodel which contain synthetic key but don't know how to resolve this issue.Linktable will work here?&lt;/P&gt;&lt;DIV class="mceNonEditable lia-copypaste-placeholder"&gt;&lt;DIV class="mceNonEditable lia-copypaste-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="mceNonEditable lia-copypaste-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Sat, 16 Nov 2024 19:28:41 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Datamodel/m-p/1656691#M730241</guid>
      <dc:creator>rupaliqlik</dc:creator>
      <dc:date>2024-11-16T19:28:41Z</dc:date>
    </item>
    <item>
      <title>Re: Datamodel</title>
      <link>https://community.qlik.com/t5/QlikView/Datamodel/m-p/1656698#M730242</link>
      <description>&lt;P&gt;Link table may work but synthetic key s are effectively link tables that qlik creates automatically.&lt;/P&gt;&lt;P&gt;I dont know if there will be any performance benefits using link tables. You will need to try and see.&lt;/P&gt;&lt;P&gt;synthetic key (simple ones) it self does cause performance issues but looking at the data model it points to a data modelling issue. maybe you need to combine a few of the tables together.&lt;/P&gt;&lt;P&gt;to put simply there is no easy answer.&lt;/P&gt;</description>
      <pubDate>Wed, 11 Dec 2019 17:28:24 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Datamodel/m-p/1656698#M730242</guid>
      <dc:creator>dplr-rn</dc:creator>
      <dc:date>2019-12-11T17:28:24Z</dc:date>
    </item>
    <item>
      <title>Re: Datamodel</title>
      <link>https://community.qlik.com/t5/QlikView/Datamodel/m-p/1656707#M730243</link>
      <description>&lt;P&gt;Do the rows represent employees enrolled in those plans, or are they just plan data?&lt;/P&gt;&lt;P&gt;-Rob&lt;/P&gt;</description>
      <pubDate>Wed, 11 Dec 2019 17:51:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Datamodel/m-p/1656707#M730243</guid>
      <dc:creator>rwunderlich</dc:creator>
      <dc:date>2019-12-11T17:51:39Z</dc:date>
    </item>
    <item>
      <title>Re: Datamodel</title>
      <link>https://community.qlik.com/t5/QlikView/Datamodel/m-p/1659087#M730244</link>
      <description>&lt;P&gt;Have a look at the following Design Blog post, believe it should help you sort out the synthetic keys:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.qlik.com/t5/Qlik-Design-Blog/Synthetic-Keys/ba-p/1472634" target="_blank"&gt;https://community.qlik.com/t5/Qlik-Design-Blog/Synthetic-Keys/ba-p/1472634&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Here is the base Design Blog link in case you want to search for other posts that may be helpful on your own:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.qlik.com/t5/Qlik-Design-Blog/bg-p/qlik-design-blog" target="_blank"&gt;https://community.qlik.com/t5/Qlik-Design-Blog/bg-p/qlik-design-blog&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Regards,&lt;BR /&gt;Brett&lt;/P&gt;</description>
      <pubDate>Wed, 18 Dec 2019 16:53:51 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Datamodel/m-p/1659087#M730244</guid>
      <dc:creator>Brett_Bleess</dc:creator>
      <dc:date>2019-12-18T16:53:51Z</dc:date>
    </item>
    <item>
      <title>Re: Datamodel</title>
      <link>https://community.qlik.com/t5/QlikView/Datamodel/m-p/1659099#M730245</link>
      <description>&lt;P&gt;If all tables are supposed to be linked, create a unique field that is common for all of them by which they will be connected and rename each of these common&amp;nbsp;fields specifically to each table. You cannot have the same column name&lt;U&gt;&lt;STRONG&gt;s&lt;/STRONG&gt;&lt;/U&gt; appear in multiple tables because Qlik links table by fields that are named alike.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Dec 2019 17:39:49 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Datamodel/m-p/1659099#M730245</guid>
      <dc:creator>jduenyas</dc:creator>
      <dc:date>2019-12-18T17:39:49Z</dc:date>
    </item>
  </channel>
</rss>

