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

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Loop Error In Processing

Hello,

I received this error when processing my QVW file.  I noticed the dotted line in my table viewer (see attached).  Can someone give me a pointer on how to eliminate this error?  What is the conseqences of ignoring this error?

Your help is much appreciated!

2 Replies
Not applicable
Author

Dotted lines are synthetic keys, automade by QlikView. You can (should) eliminate them by creating keys for QlikView to use. Search on synthetic keys and you will find a ton of useful tips.

johnw
Champion III
Champion III

Dotted lines are not synthetic keys.  Dotted lines are associations that QlikView has "removed" because your data structure has a loop.  To fix it, remove the loop.

But I'll agree with Thomas that you should remove the synthetic keys as well.  Synthetic keys are rarely a problem when you know what you're doing and put them in your model intentionally, but given your lack of understanding of the loop, I'd bet that your synthetic keys are accidental mistakes instead of intentional links.

Basically, your data structure appears to be very badly broken, and almost certainly needs to be fixed.  This isn't the kind of thing you ignore.  But I don't know your data or current data structure, so I can't fix it for you.  And really, giving you the right or best data structure would likely take more familiarity with your data than I care to achieve.

I can give a general rule of thumb, though, which is to try to model your data as a fairly simple star or snowflake schema.  In other words, try to create a central fact table, and link any helper tables directly to that central table via association on a single field.  That would be a star schema.  If you have some helper tables that really need helper tables themselves, then go another level out, and you have a snowflake schema.

Like any rule of thumb, this may not be the best way to model some specific data.  But it tends to be something that works well for most people most of the time in QlikView.