My table relationships have become too complicated, how can I simplify it?

[Anonymous]

Hi,

I have an application that I'm developing, which will be used by people to analyse our relationship with competitors in the market.  It was working fine until I attempted to link the new competitor data with our product data (linked via the 'matches' table).

It has now stopped working.  The main table on my landing screen should display the company brands as a dimension and the number of product matches as an expression (with some other things as well) but it no longer does.  It was working fine before.

I've checked that there are no bad field names in the expressions, so the fault can't be there.  The only thing I can think is that my table relationships are too complicated.  Qlik has created another table ($Syn 3) just to link together some of the tables.  I've attached an image of the table viewer (and taken out some confidential information), do you think that this is the route of the problem?  Or is there another issue I haven't thought of?

Thanks

[vinieme12 · Accepted solution]

avoid Synthetic keys

Create a BridgeTable that connects to Orders  & Competitor

And Product Connect to Orders

[rahulpawarb]

Hello Henry,

Turst that you are doing good!

There are three synthetic keys in your data model:

1. PK_SKU, PK_Orders_Key, PK_Key

2. PK_SKU, PK_Key

3. PK_SKU, PK_Orders_Key

As per my primary analysis there are three different tables causing creation of synthetic keys i.e. Scrape, Matches & Orders. To make the data model more simplified you have to remove the synthetic keys.

If you are using multiple fact tables with different data grain then go ahead and make use of LINK TABLE.

Refer below links for link table concepts:

http://www.learnallbi.com/link-table-in-qlikview/

If you need further help then please share the application with sample data. It will help us to provide you expected response with quick turnaround.

Regards!

Rahul

[psk180590]

Hello Henry,

Just to add up to the above suggestions.

Decide upon one Primary key and you could use Alias names for the Fields that are turning into Synthetic keys.