topic Re: Script data in Connectivity & Data Prep

Script data

Viviane — Mon, 25 Apr 2022 14:18:47 GMT

Hello,

I made a script to load my two documents on qliksense. Qliksense recognized 2 synthetic keys between my 2 tables, so there is a link between the 2 tables. But when I create visualizations with one of the 2 tables, the data is displayed correctly. Once I filter my data, one of the tables does not update and displays as if there is no data when there is not...

Thank you very much for the help,

Viviane

Re: Script data

canerkan — Mon, 25 Apr 2022 14:47:03 GMT

Hi Viviane,

do you have any sample data and a screenshot of your data model you can provide?

Have a look at this blog post, maybe this helps.

https://community.qlik.com/t5/Qlik-Design-Blog/Synthetic-Keys/ba-p/1472634

if you geht synthetic key, you should always ask yourself if this is right. I would recomment to avoid them and build generic keys of your own. That way you will always know, how your data is associated with each other.

Regards,

Can

Re: Script data

Viviane — Tue, 26 Apr 2022 07:47:11 GMT

Can,

in attachements, you will find my model data. The link between my table 'projects' and 'organisations' are the 'id' and 'rcn'.

Thank you for the website i'm gonna check.

Regards,

Viviane

Re: Script data

canerkan — Tue, 26 Apr 2022 10:02:20 GMT

Hi Viviane,

I would recommend building your own key, since you are experiencing strange behaviour.

You can do that by combining your two fields (rcn and id) into a new field instead of loading them as separate fields, like this:

Load rcn & '_' id as %Key, ... From ...

Do that for all tables that contain both fields.

Then choose only one table where you are loading both fields separate.

What ID is contained in your field? and what data is contained is rcn?

in your screenshot there is a field "projectID" in your Table "organisation". Since you are trying to build a connection to your "project" table, wouldn't that be a better field to do that?

that way you could load your fields "id" and "rcn" only in your organisation table to avoid the synthetic key.

Let me know if it helped.

Regards,

Can