Simple association and synthetic keys seem OK, but not effective: who could explain why?

[#1]

Hello All,

I am new to qlikview and starting some tests. I just imported 3 tables from an oracle schema and let qlikview create associations based on synthetic keys (same field names). The data model is quite simple: many fabs, a fab contains many equipments, an equipment produces daily activity, and an equipment is functionally grouped per "module". Such data model is so a fact table (bo_ruuf_daily) witn 2 dimension tables (equipment and module). Here is the Table viewer result where synthetic keys ae OK:

The issue is when in the sheet I select an equipment, the according module is never selected, or when I select a module the according equipments are not selected. Seems like not associated. The other selections (fabname, daily activity) are selected fine yet.

What is wrong?

Note if I don't load the fact table (bo_ruuf_daily), I get a new Table viewer ciontent, and all is working fine (to show you that equipment/module are containing common data):

The DB data model is perhaps no the best, but is this qlikview behavior normal?

Many thanks,

Nicolas

[brenner_martina · Accepted solution]

Hi, Nicolas,

never, never, never use synthetic keys in QlikView, you have to concat fields together to define the keys:

EQUIPMENT:
Load FABNAME&'/'&MODNAME As Key1,
FABNAME&'/'&EQTNAME As Key2,
FABNAME,
MODNAME,
EQTNAME,
....
FROM Table1;

MODULE:
Load FABNAME&'/'&MODNAME As Key1,
// FABNAME,
// MODNAME,
....
FROM Table2;

BO_ROOF_DAILY:
Load FABNAME&'/'&EQTNAME As Key2,
// FABNAME,
// EQTNAME,
....
FROM Table3;

[#3]

Work fine, great.

Many thanks, Nicolas