Synthetic keys . How to remove them

[#1]

Synthetic keys . How to remove them

[senpradip007]

Remane the field name, synthetic keys would removed.

Tab1:

Load

    A as Id,

    B

From <Table Name>;

Load

     A as Serial,

     C

From <Table Name>;

[sujeetsingh]

Renaming is the one way to remove the Synthetic keys but First go to this link

Should We Stop Worrying and Love the Synthetic Key?

[#4]

thank you sujeetsingh

[#5]

Hi

Either your represent the field name with a alias or you use Qualifier statement . In some case one could even comment or ignore the fields which are not required as per your requiremnet

Thanking You

Vinayagam

[#6]

hi please go through this

[hic]

See http://community.qlik.com/blogs/qlikviewdesignblog/2013/04/16/synthetic-keys

The following can also be useful, although it is not directly about synthetic keys:

http://community.qlik.com/blogs/qlikviewdesignblog/2013/06/25/circular-references

HIC

[#8]

thankyou

[its_anandrjs]

I believe you get all information related to the synthetic keys and how to avoid them or you can refer the attached document.

http://community.qlik.com/blogs/qlikviewdesignblog/2013/04/16/synthetic-keys

[Joseph_Musekura]

Hi,

Here are three ways to get rid of Synthetic Keys

1. Using QUALIFY

This enforces QlikView to qualify all/selected fields. Qualify implements the check on full path of the field (e.g. Field is designated by Tablename.FieldName).

2. Autonumber

If you need to concat the Syn Key candidate fields and create your own key, you can use Autonumber/Autonumberhash128/Autonumberhash256 function. This will create a unique integer value for each distinct combination of the concateneted columns.

Autonumberhash128 and Autonumberhash256 creates 128bit and 256bit values respectively.

One word of cauton using Autonumber is, as they are system generated, you do not have any control over the values. And for external QVDs, since the range of unique autonumber values are limited, uniqueness is not guranted. the hash128 and hash256 functions particularly address this issue and widens the range to ensure uniqueness.

3. Aliasing

If you alias the comflicting fields, i.e. the Syn Key candidate fields, they would be treated as different fields and will not be joined automatically by QV. This is a simple solution based on how flexible the requirements are, in renaming the fields.

Ofcourse you will find many other examples in this forum/QV manual that will strenthen your concept. This is my understanding from my experience with QV. Please let me know if it answers your question on my post.

You can read more from

http://community.qlik.com/message/183143#183143

/joseph