qualify keyword

[#1]

hi

i am using 6 different tables product ,orderdetails etc. i have productid and unitprice columns in  product and orderdetails table thats why synthetic key issue is troubling me. i used qualify keyword

qualify productid,unitprice;

load statement of product

load statement for other tables

load orderdetails.

when i used qualify keyword like this in that case my unitprice column was showing no values means it became unavailable.

when i use qualify productid;

load product

load other tables

qualify unitprice;

load orderdetails

it worked....

why did this happen??

any problem with using qualify keyword???

i am attaching a pic for better understanding..

[CELAMBARASAN]

Hi,

     Is unitPrice is same in both product and order details table for the products?If so why not you remove the unit price field from order details field?

Celambarasan

[#3]

i think i can it with the as keyword.

but my problem is lot worse i am facing both synthetic key issues and loosely coupled table i am attaching with it the snap of the schema... please help me tackling this issue

[CELAMBARASAN]

Hi,

     Attach Full schema.In the attached schema only synthetic exists there is not loosely coupled table.

Or post your complete script.

Celambarasan

[#5]

[#6]

qlik view is telling me that invoices is a loosely coupled table and when i made a selection in productid of product,corresponding values in invoices didnt get selected..why and how to solve it?

[#7 · Accepted solution]

For a start, it looks like you need to qualify PostalCode also as you are causing a circular relationship which is causing the loosely coupled table.

[#8]

thnx Matt

i think oderid is also causing the loosely coupled table situation am i rite?

[#9]

I don't think so I think. It looks like OrderID is only acting as a relationship between the orders and their order lines which I expect is correct.