topic Re: synthetic keys in QlikView

synthetic keys

Anonymous — Tue, 30 Dec 2014 09:09:16 GMT

if we join two tables from different datasources one from oracle db and other from excel .If the join two tables have two common fields .will synthetic key will be formed or not ?

Re: synthetic keys

Tue, 30 Dec 2014 09:15:13 GMT

hi rgv,

yes synthetic keys will be formed. use qualify* function to eliminate them. unqualify the key fields alone.

hope it helps.

regards,

Barathiraja

Re: synthetic keys

rajeshvaswani77 — Tue, 30 Dec 2014 09:15:18 GMT

If there is a single field that is common across tables then no synthetic key. it will create a natural join.

In case if more than 1 field is common, then it will create a synthetic key. The common fields will move to a third table that is a synthetic table. The name of the table will contain syn.

thanks,

Rajesh Vaswani

Re: synthetic keys

francoiscave — Tue, 30 Dec 2014 09:15:41 GMT

Hi Rgv rand,

Yes absolutely...

Make a "concatenation key" like : field1&'|'&field2 as %Key_Field

to solve this issue.

Best Regards,

François

Re: synthetic keys

Tue, 30 Dec 2014 09:16:50 GMT

it doesn't matter from which source u have loaded data.

after loading data in to qlikview if both tables having common key fields then synthetic key will occur.

Re: synthetic keys

engishfaque — Tue, 30 Dec 2014 09:20:58 GMT

Dear rgv,

Yes, synthetic key will be created.

Here are the ways through which you can avoid from Synthetic key,

1. Rename fields name by using Rename Clause, AS Clause or Qualify/UnQualify,

2. Concatenate to both tables or create Link table.

Kind regards,

Ishfaque Ahmed

Re: synthetic keys

Anonymous — Tue, 30 Dec 2014 09:22:20 GMT

If tables not able to concatenate use the link table concepts

http://community.qlik.com/blogs/qlikviewdesignblog/2013/05/17/concatenate-vs-link-table

Re: synthetic keys

Tue, 30 Dec 2014 11:26:22 GMT

Yes,

it doesn't matter from which source u have loaded data.

After loading data in to qlikview if both tables having common key fields then synthetic key will occur.

You can reslove this issue in below ways

1)Alias(Rename the field)

2) Comment the feild(Check with client is this field required for future, before commenting)

3) Use Qualify Key word

4) Concatinate(Forced).

Chose any of the above option for this.