Unique numeric key for several fields in different loads

[warfollowmy_ver]

Hello.

As I understand the functions of the autonumber (+ hash***) correctly create a numeric key only within a single load, because it depends on the sorting of the data and the order of reading from the table. https://help.qlik.com/en-US/qlikview/November2017/Subsystems/Client/Content/Scripting/CounterFunctio...

For a unique key in different downloads, you need to use the hash function without an autonumber (hash). But then you get a string of 43 characters, mostly in terms of the amount of data it's much worse than just concatenating several fields.

Are there other ways to make a compact unique numeric key in different loads?

[marcus_sommer]

Maybe you could use an approach like this one: Re: Convert concatenated numbers to num

- Marcus