Skip to main content

New to Qlik Sense

If you’re new to Qlik Sense, start with this Discussion Board and get up-to-speed quickly.

Announcements
Welcome to Qlik Community! Check out our new navigation! FIND OUT MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
JasonKKA
Contributor II
Contributor II

Syn-key from QueryResult Table

Good morning Experts,

I am facing an unprecedented situation in which a syn key is generated after the data has completed loading from the data load editor. The syn key arises from a table called 'QueryResult', which I am very sure I did not code for in the data load editor (and I verified this through the Search function in the data load editor). The conflicting fields in this QueryResult table with my main fact table are from a table which I had specifically dropped in the script, but somehow reappears and renamed as this 'QueryResult' table.

Anybody faced a similar situation or know how to simply remove this table (from nowhere)?

Thank you very much in advance,

Jason

 

Labels (4)
1 Solution

Accepted Solutions
JasonKKA
Contributor II
Contributor II
Author

I managed to know the issue in the end; it was a duplicated code for another left join which resulted somehow in the automated formation of this extra table. Thank you for all your help.

View solution in original post

5 Replies
sidhiq91
Specialist
Specialist

@JasonKKA  If you had dropped the table, then the chances of Syn Key creation is not a possibility. If possible please share the code and I will have a look at it.

Rishabh_Chaudhary
Partner - Contributor
Partner - Contributor

Use Exit Script after your table data load query. See if it fixes this issue. 

JasonKKA
Contributor II
Contributor II
Author

Hi @sidhiq91 , the code is very long and it is not very feasible to share it. In short, the table that was dropped is not the issue, but rather the new autogenerated table containing some of the fields from the dropped table (these fields were specifically left joined from another table that was not loaded in the script) that is creating the syn key. 

JasonKKA
Contributor II
Contributor II
Author

Thanks @Rishabh_Chaudhary , but this did not fix the issue.

JasonKKA
Contributor II
Contributor II
Author

I managed to know the issue in the end; it was a duplicated code for another left join which resulted somehow in the automated formation of this extra table. Thank you for all your help.