Qlik Community

Qlik Sense App Development

Discussion board where members can learn more about Qlik Sense App Development and Usage.

Not applicable

Avoid synthetic keys

Hi.

I have a problem with the following scheme:


Table A

ERPOthers
X
Y

Table B

ITEMOthers
A
B

Table C

ERPITEMOthers
XA
XB

Table D

ERPITEMOthers
YB
XA

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

2 Replies
MVP
MVP

Re: Avoid synthetic keys

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);


Capture.PNG

MVP
MVP

Re: Avoid synthetic keys

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?