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

Announcements
Want to see what's currently in public preview? We've pulled it all together in one place. Check it out here
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Remove loops

I have two fact tables : Budget and vente .

I create a link table to store them but I get loops between tables as it's shown in the following picture .

Sans titre.png

How to remove loops ?

Labels (1)
7 Replies
Colin-Albert
Partner - Champion
Partner - Champion

Please don't post the same question multiple times. This question has been posted twice today already!

senpradip007
Specialist III
Specialist III

Your image is not clear. Please upload a fresh copy.

Colin-Albert
Partner - Champion
Partner - Champion

Rename the field "Code Rayon" in either the Budget or Merchandise table.

This will remove the loop.

Anonymous
Not applicable
Author

it returns wrong results

Colin-Albert
Partner - Champion
Partner - Champion

Then you will need to include the field in your link table so the association is correct. Otherwise consider concatenating your budget and sales data to a single table.

Anonymous
Not applicable
Author

How to include the field in the link table , I am a newbie with qlikview .How can I concatenate the two table sales and budget , It doesn't have the same columns

kuczynska
Creator III
Creator III

Check this article: Understanding Join, Keep and Concatenate

You have few options to remove the loops - rename, remove, join/concatenate tables. You can try to use QUALIFY function at the beginning of the load script to add the prefix (parent table name) to each field name (this will create a set of separate tables) and than slowly build your way up - by UNQUALIFYING the fields that are creating logical associations between tables. As you know, some of the loops might still exist in your data model as that could also be a result of the bad architecture of the model, but in that case there must be a logical/business reason for that kind of implementation. Good luck!