Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Dear Friends,
I have create a file which has table links as below. I think there should be an error in this configuration. I guess that it can be fix with a JOIN statement but I don't know how to make it. Would you please help me about fixing the links. Sampledata must be in the center of the schema.
Hope to hear you soon.
Best Regards,
The thing is that QlikView will automatically form a link between tabes where the same field name exists, and when that field name exists in more than two tables, it will create a looping link between all three tables and the results you see will be a little difficult to predict.
The other way to achieve it is to create a link table in the middle of all three tables, the link table will just contain key values that are not used in objects, this table could then link to the other three tables. This is, in my opinion, simply introducing more complexity when its not required. When I come across these issues I simply name the fields that I don't want to use as something that will come right down the bottom of the field list, for example, you only want to have TARHI available, and I have introduced MASTER_TARHI into the app, I would normally name the second value something like ZZZ_TARHI_KEYVALUE so that its obvious to me that we shouldn't use it in objects.
Not sure if this helps, but it is what it is.......
Try attached
Let me know if this is what you were expecting to see, and if not, a little more info on what you want.
Cheers,
Dear Nigel,
Thanks for your support. But I don't want to use 2 date field on my sample data. Are there any oher way to put te sample data table on the center of the table schema?
Best Regards,
The thing is that QlikView will automatically form a link between tabes where the same field name exists, and when that field name exists in more than two tables, it will create a looping link between all three tables and the results you see will be a little difficult to predict.
The other way to achieve it is to create a link table in the middle of all three tables, the link table will just contain key values that are not used in objects, this table could then link to the other three tables. This is, in my opinion, simply introducing more complexity when its not required. When I come across these issues I simply name the fields that I don't want to use as something that will come right down the bottom of the field list, for example, you only want to have TARHI available, and I have introduced MASTER_TARHI into the app, I would normally name the second value something like ZZZ_TARHI_KEYVALUE so that its obvious to me that we shouldn't use it in objects.
Not sure if this helps, but it is what it is.......