topic Avoid synthetic keys in App Development

Avoid synthetic keys

Tue, 10 May 2016 19:07:26 GMT

Hi.

I have a problem with the following scheme:

Table A

ERP	Others
X
Y

Table B

ITEM	Others
A
B

Table C

ERP	ITEM	Others
X	A
X	B

Table D

ERP	ITEM	Others
Y	B
X	A

By making the load several synthetic keys are produced , because there are two tables with two fields with the same name, which are related to Tables A and B.

C and D are differents tables between them.

What can i do to fix the problem and keep the idea of the scheme ?

a greeting

Re: Avoid synthetic keys

sunny_talwar — Tue, 10 May 2016 19:22:34 GMT

May be like this:

Table1:

LOAD ERP,

Others as Others1

FROM

[https://community.qlik.com/thread/216315]

(html, codepage is 1252, embedded labels, table is @1);

Table2:

LOAD ITEM,

Others as Others2

FROM

[https://community.qlik.com/thread/216315]

(html, codepage is 1252, embedded labels, table is @2);

Table3:

LOAD AutoNumber(ERP & ITEM) as Key,

Others as Others3

FROM

[https://community.qlik.com/thread/216315]

(html, codepage is 1252, embedded labels, table is @3);

Table4:

LOAD AutoNumber(ERP & ITEM) as Key,

ERP,

ITEM,

Others as Others4

FROM

[https://community.qlik.com/thread/216315]

(html, codepage is 1252, embedded labels, table is @4);

Re: Avoid synthetic keys

swuehl — Tue, 10 May 2016 21:44:31 GMT

It's hard to give any advice without knowing what you want to model and if all fields with the same name describe an entity with the same role or a different role.

Have a look at

Circular References

Have you also considered just concatenating Table C and Table D?