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

Announcements
Qlik Connect 2026! Turn data into bold moves, April 13 -15: Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

syntheic key issue

can any one help me to genrate script for link table to resolve the issue in the attatched file.

i have two dimension partno and stockist and two fact purchase and recipt.

how to genrate the script for link table while my dimension and fact is loading from qvd how to tackel residence command.

1 Solution

Accepted Solutions
Not applicable
Author

See the attached file. You have to reload it first. Think it should work like this.

Best regards,

William

View solution in original post

6 Replies
CELAMBARASAN
Partner - Champion
Partner - Champion

Hi,

     I cann't open your file because of personal edition user.

     I assume that your problem is synthetic key.

     To eliminate synthetic key Join the 2 fields and make that as key bet 2 tables.

     Then use qualify for that 2 fields.

     For example

     qualify product,billno;

     Table1:

     Load

          product & billno as Key,

          product,

          billno

     From..

     Table2:

     Load

          product & billno as Key,

          product,

          billno

     From..

Celambarasan

jagan
Partner - Champion III
Partner - Champion III

Hi,

Just paste the script or attach the screenshot of the mapping diagram, it helps in understanding the problem.

Regards,

Jagan.

Not applicable
Author

See the attached file. You have to reload it first. Think it should work like this.

Best regards,

William

Not applicable
Author

absulutly perfect William..

thnks alot.

Not applicable
Author

wht if i have

three same column but one filed is differnet say:

1st cube:

employee_id

location

item

supplier_id

purchase_Cost

2nd cube:

employee_id

location

item

customer_id

sold_Cost

how to manage this.............

CELAMBARASAN
Partner - Champion
Partner - Champion

If my understanding is correct then both the tables meaning is different

1st is about purchase

2nd is about sold then u can ve it has separate

1st cube:

employee_id

location AS PurchaseLoc

item AS PurchaseItm

supplier_id

purchase_Cost

2nd cube:

employee_id

location AS SaleLoc

item AS SaleItm

customer_id

sold_Cost

If i'm wrong let me know

Celambarasan