topic Re: Synthetic keys in QlikView

Synthetic keys

trishita — Wed, 25 Nov 2020 16:16:04 GMT

I have joined two tables based on intervalmatch function

General Information:

LOAD *
FROM
[MO_BUN_SUR_SURVEY_VIEW.qvd]
(qvd);

Sounding Correction:

LOAD *

FROM
[mo_purch_sounding_correction_view.qvd]
(qvd);

Inner Join

INTERVALMATCH (SURVEY_DATE,IMO_NO) SELECT SOUNDING_START_DATE,SOUNDING_END_DATE,IMO_NO

resident Sounding Correction;

The table is joined but I have one issue:I have one problem that there are 2 synthetic keys created .In 1 table which contains only IMO No and Survey ID and the other synthetic key table which contains all other fields.As I am new to Qlikview is it advisable to drop the other synthetic keys which are not the main keys?

Re: Synthetic keys

datanibbler — Fri, 11 May 2018 09:15:27 GMT

Hi,

this looks like a double post?

Anyway - if they are not necessary for linking the tables, drop the synthetic keys.

Re: Synthetic keys

trishita — Fri, 11 May 2018 11:36:50 GMT

I solved this problem using qualifiers:

Qualify *;

Unqualify SOUNDING_START_DATE,SOUNDING_END_DATE,IMO_NO;

SoundingCorrections:

LOAD *

FROM
[mo_purch_sounding_correction_view.qvd]
(qvd);