Qlik Community

New to Qlik Sense

Discussion board where members can get started with Qlik Sense.

flygstolen_fred
New Contributor III

Synthetics keys

Hi,

My app "complain" about use of synthetics keys during the data load process.

Is this possible to solve in a better way and avoid synthetics keys warning? I wanna be able to compare the Reservation data with the Search data and drill down based on geographic's and Supplier. Any help are very appreciated!

Reservation:

LOAD

ReservationId,

Name,

ReservationDate,

TotalPrice,

Supplier,

DestinationCityName;

Search:

LOAD

SearchId,

SearchDate,

Date1,

Date2,

Supplier,

DestinationCityName;

DestinationGEO:

LOAD

    CityName as DestinationCityName,

    CountryCode as DestinationCountryCode,

    CountryName as DestinationCountryName,

    ContinentCode as DestinationContinentCode,

    ContinentName as DestinationContinentName

FROM [lib://Statistics Export Folder/geo.csv]

Message was edited by: fredrik olsson

1 Solution

Accepted Solutions

Re: Synthetics keys

Maybe concatenate the first 2 tables into a single table :

Facts:

LOAD

ReservationId,

Name,

ReservationDate,

TotalPrice,

Supplier,

DestinationCityName

;

Concatenate {Facts]

LOAD

SearchId,

SearchDate,

Date1,

Date2,

Supplier,

DestinationCityName

;

DestinationGEO:

LOAD

CityName as DestinationCityName,

CountryCode as DestinationCountryCode,

CountryName as DestinationCountryName,

ContinentCode as DestinationContinentCode,

ContinentName as DestinationContinentName

FROM [lib://Statistics Export Folder/geo.csv]

;



I presume in your real load script you first load loads do indeed load form somewhere.

18 Replies
rittermd
Honored Contributor

Re: Synthetics keys

I'm not seeing where you would get a synthetic key.  The only field in common is DestinationCityName between the 3 tables.

Can you load a screen shot of what you are seeing?

vinieme12
Esteemed Contributor II

Re: Synthetics keys

flygstolen_fred
New Contributor III

Re: Synthetics keys

Hi Mark,

Sorry, missed one of the common fields (supplier), added it now. Is there any easy way to avoid it?

$Syn 1 = DestinationCityName+Supplier

flygstolen_fred
New Contributor III

Re: Synthetics keys

Thanks Vineeth for trying to help, but I couldn't find any solution to my problem in the videos.

jaceknoden
Contributor

Re: Synthetics keys

Hello Fredrik,

Two options:

1. You should ues "as" , so Supplier as Search_Supplier

2.

QUALIFY *;

UNQUALIFY 'DestinationCityName';

and on the end of script UNQUALIFY *;

Regards

Jacek.

flygstolen_fred
New Contributor III

Re: Synthetics keys

Thanks for trying to help out,

Will I be able to compare Searches against Reservations based on geographics and supplier by using different names for the supplier field?

Best,

Fredrik

jaceknoden
Contributor

Re: Synthetics keys

Fredrik, could you provide a sample of app to the better understanding?

Regards

Jacek.

Re: Synthetics keys

Maybe concatenate the first 2 tables into a single table :

Facts:

LOAD

ReservationId,

Name,

ReservationDate,

TotalPrice,

Supplier,

DestinationCityName

;

Concatenate {Facts]

LOAD

SearchId,

SearchDate,

Date1,

Date2,

Supplier,

DestinationCityName

;

DestinationGEO:

LOAD

CityName as DestinationCityName,

CountryCode as DestinationCountryCode,

CountryName as DestinationCountryName,

ContinentCode as DestinationContinentCode,

ContinentName as DestinationContinentName

FROM [lib://Statistics Export Folder/geo.csv]

;



I presume in your real load script you first load loads do indeed load form somewhere.

flygstolen_fred
New Contributor III

Re: Synthetics keys

Hi Mark,

The app is "full" of other things, but I created a new one to visualize the problem I get. Does this help you?