Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
trishita
Creator III
Creator III

Synthetic keys

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?

1 Solution

Accepted Solutions
datanibbler
Champion
Champion

Hi,

this looks like a double post?

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

View solution in original post

2 Replies
datanibbler
Champion
Champion

Hi,

this looks like a double post?

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

trishita
Creator III
Creator III
Author

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