<?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 regarding keys in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/regarding-keys/m-p/258259#M1204408</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;DIV&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;In QlikView the links between tables are made based on the field names. A surrogate key is the best candidate for this.&lt;/P&gt;&lt;P&gt;Be careful to end up in correct links by unintentinally use the same field names (e.g. Short_Desc etc)&lt;/P&gt;&lt;P&gt;You can have the table name added to the fields using QUALIFY to prevent such unwanted links. You can also use a pattern for link fields, e.g. add a "%" in front, to make them stand out. In this case you can QUALIFY all fields but UNQUALIFY "%*". There are some examples in the documentation.&lt;/P&gt;&lt;P&gt;SCD handling is mostly left to your app with some built in functions that help to deal with them like intervalmatch.&lt;/P&gt;&lt;DIV&gt;I have attached a simple example of an SCD2 case.&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Regards&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Jürg&lt;/DIV&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 19 May 2010 14:19:54 GMT</pubDate>
    <dc:creator />
    <dc:date>2010-05-19T14:19:54Z</dc:date>
    <item>
      <title>regarding keys</title>
      <link>https://community.qlik.com/t5/QlikView/regarding-keys/m-p/258258#M1204407</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;How to generate a key field in qlikview??? How qlikview will handle the surrogate keys??? how does qlikview handle slowly changing dimensions???&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 May 2010 12:20:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/regarding-keys/m-p/258258#M1204407</guid>
      <dc:creator />
      <dc:date>2010-05-19T12:20:31Z</dc:date>
    </item>
    <item>
      <title>regarding keys</title>
      <link>https://community.qlik.com/t5/QlikView/regarding-keys/m-p/258259#M1204408</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;DIV&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;In QlikView the links between tables are made based on the field names. A surrogate key is the best candidate for this.&lt;/P&gt;&lt;P&gt;Be careful to end up in correct links by unintentinally use the same field names (e.g. Short_Desc etc)&lt;/P&gt;&lt;P&gt;You can have the table name added to the fields using QUALIFY to prevent such unwanted links. You can also use a pattern for link fields, e.g. add a "%" in front, to make them stand out. In this case you can QUALIFY all fields but UNQUALIFY "%*". There are some examples in the documentation.&lt;/P&gt;&lt;P&gt;SCD handling is mostly left to your app with some built in functions that help to deal with them like intervalmatch.&lt;/P&gt;&lt;DIV&gt;I have attached a simple example of an SCD2 case.&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Regards&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Jürg&lt;/DIV&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 May 2010 14:19:54 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/regarding-keys/m-p/258259#M1204408</guid>
      <dc:creator />
      <dc:date>2010-05-19T14:19:54Z</dc:date>
    </item>
  </channel>
</rss>

