topic Re: Date as 'key for linkage' issue in QlikView

Date as 'key for linkage' issue

arpitkharkia — Wed, 19 Oct 2016 10:38:40 GMT

Hi all,

Currently im working on a project which has three tables. The data source of these three tables is an excel file. All these tables have date field in common apart from one other field. I want a combination of the two as my key so as to remove synthetic key.

The issue im facing is that all the three date fields are in different range. For example if one date say 14-10-2016 is present in table A then its not present in the other two and vice versa. So after combing the two keys all the data is not linked with each other properly as I may select some date which is not present in other tables hence missing out on data.

Looking for solution asap!

Re: Date as 'key for linkage' issue

Nicole-Smith — Wed, 19 Oct 2016 16:55:00 GMT

If you have ranges/intervals with start and end dates, you'll want to look at using IntervalMatch ‒ QlikView.

Re: Date as 'key for linkage' issue

arpitkharkia — Thu, 20 Oct 2016 04:36:25 GMT

Thanks for your help!

Re: Date as 'key for linkage' issue

cotiso_hanganu — Thu, 20 Oct 2016 08:34:23 GMT

But if you don't have intervals, but all your 3 sets of data have facts that share some other columns in common (like article, category, etc), perhaps you should think to force a concatenation of the 3 tables and create a fat single table, with some aligned columns and some columns that are populated only in certain parts of the resulting table.

PS: Don't worry on the Qlik performance, QIX and AQL engines are very good in ignoring the NULLs.

Re: Date as 'key for linkage' issue

arpitkharkia — Thu, 20 Oct 2016 09:01:19 GMT

Thank you so much for the suggestion. Going to follow this solution!