<?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: Function to generate unique number/key in load script in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Function-to-generate-unique-number-key-in-load-script/m-p/515488#M192478</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Use Hash128/160/256. These functions has a very low chance of colision&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 02 Dec 2013 15:28:38 GMT</pubDate>
    <dc:creator>Clever_Anjos</dc:creator>
    <dc:date>2013-12-02T15:28:38Z</dc:date>
    <item>
      <title>Function to generate unique number/key in load script</title>
      <link>https://community.qlik.com/t5/QlikView/Function-to-generate-unique-number-key-in-load-script/m-p/515487#M192477</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I need to generate unique numbers/keys to replace a lengthy a concatenated key in the load script.&lt;/P&gt;&lt;P&gt;The unique number should be consistant and should persist reloads across different files. I'm not sure if autonumber() meets the requirement. I remember reading that it does not retain uniqueness. please advice.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Dec 2013 15:16:26 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Function-to-generate-unique-number-key-in-load-script/m-p/515487#M192477</guid>
      <dc:creator />
      <dc:date>2013-12-02T15:16:26Z</dc:date>
    </item>
    <item>
      <title>Re: Function to generate unique number/key in load script</title>
      <link>https://community.qlik.com/t5/QlikView/Function-to-generate-unique-number-key-in-load-script/m-p/515488#M192478</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Use Hash128/160/256. These functions has a very low chance of colision&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Dec 2013 15:28:38 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Function-to-generate-unique-number-key-in-load-script/m-p/515488#M192478</guid>
      <dc:creator>Clever_Anjos</dc:creator>
      <dc:date>2013-12-02T15:28:38Z</dc:date>
    </item>
    <item>
      <title>Re: Function to generate unique number/key in load script</title>
      <link>https://community.qlik.com/t5/QlikView/Function-to-generate-unique-number-key-in-load-script/m-p/515489#M192479</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I agree with Clever, to do what you're asking, the best option is HashXXX().&amp;nbsp; Unless you're dealing with rows in the billions, I'd recommend Hash128.&amp;nbsp; The only drawback that you'll find is that each unique instance requires 16 bytes (for Hash128, 160 is 20 bytes and 256 is 32 bytes per unique instance).&amp;nbsp; This shouldn't be an issue if you are storing tables into QVD, but I would suggest wrapping an AutoNumber(hash_field, 'key_name') around your hashed fields when loading into an application meant for user consumption.&amp;nbsp; It may slow down your reloads a little bit, but it will consume a lot less memory on load and should perform better.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Dec 2013 15:36:52 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Function-to-generate-unique-number-key-in-load-script/m-p/515489#M192479</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2013-12-02T15:36:52Z</dc:date>
    </item>
  </channel>
</rss>

