Skip to main content
Announcements
Qlik Community Office Hours, March 20th. Former Talend Community users, ask your questions live. SIGN UP
cancel
Showing results for 
Search instead for 
Did you mean: 
francofiorillo
Partner - Creator
Partner - Creator

Loading problem with 10 Qlikwiew

Hello.
It happens to me a strange thing.
With the release of version 10, I started to try the applications already made.
I had no problem, except for an application for which I can not reload the script as though not getting any error message from the variables, and showing that you have loaded the data, in the end I said:
Running the script failed. Load the previous data?
I have tested.
1. I tried to load only part of the script. To a certain extent is fine, then randomly just add another sheet of the script gives me the error persists, oddly enough, even if I delete the package you just added.
2. I tried to export the presentation of the document and to import it into a new document. Well. The data load is successful only the first time, then I always get the same error.
I think there are dirty data. In the script, do not use anything special. Can I assume that would be the command RESIDENT (I have several).
Could you please give me a hint?

thanks in advance for your cooperation

31 Replies
Not applicable

Just an add....

Any change show me 'Duplicate keys when loading Input Field'.

Not applicable

I think schiesslr nailed it with his point 1. This should explain why some many people here are having an issue. It's not that QV10 has a bug, it's that with the QV10 release the user is warned that they are making a mistake in their data model.

Make sure the table that contains the input field has a unique key. If not you will get the "Duplicate keys" error. Think of it in this way:

Qlikview is bacially storing a value unique to the row in your table. If there is no single column that uniquely defines a row, then QV has no way to properly determine which row it should update. The core idea with input fields is that your input value should only modify one row. This is why so may people are finding a solution by adding the RowNo() function as the last column in thier table - because this create a unique ID for the row that did not exist before.

My opinion is that adding RowNo() is an incorrect solution and you should really look at your data model and understand what your primary key should be on the table you are attempting to add input fields to. Most probably this investigation will yield a much more valuable primary key than an arbitrary RowNo().