Problem with inputfields on qlikview 10

[tduarte]

We had an document on v8.5 that was having performace issues so we decided to have a go with QV10.

After reloading the document in QV10 I realized not everything was working,  mainly the inputfields.

I found someone suggesting here that we should always had an unique ID to avoid issues with inputfields. So I used Rowno() in the table that contain the inputfield and it all looked fine. But it wasn't!

We load the inputfields with a default value of '0'. After a reload that value is keept but even if you save the document, close and then when you reopen it , the inputfield will have values from 0, 1, 2, 3, ... onwards...

It sets values to the inputfield just by closing an reopening the document.

Has anyone experienced this? Any ideas of what needs to be done to fix it?

[tduarte · Accepted solution]

Hi HD,

Yes, exactly. I'm using the same method as suggest recently by support.

Inputfield MyInputField;

Data:

Load

      *,

     RowNo() as InputKey

From data.csv;

InputField:

Load

      RowNo() as InputKey,

     '0' as MyInputField // sets 0 as default value in my case

AUTOGENERATE peek('InputKey', -1, 'Data');

It works.

Regards,

Telmo

[hdonald]

Telmo,

I was doing the load 'From data.csv' bit twice but that 'AUTOGENERATE peek(....' solution looks much neater, thanks for posting it,

Regards,

HD

[bob_zagars]

Support,

We have determined in the Developer II training class for version 10 that SR3 is causing the problem with INPUTFIELD's.  Several of the students had the same problem and other's did not after researching we found that the problem was only with SR3.  The other students had SR1 and SR2.  Hope this helps resolve this problem.

Regards,

Bob

[amien]

Thanks for this workaround

Anyone tested this with QV11 IR? cause from what i tested, it also didn't work

[#6]

We have tested the problem in IR QlikView version 11 and also gives memory problem on the server reloads.

Is there any recommendation or limitation by the manufacturer?

[Anonymous]

I had the issue with v10 SR3.

When I opened the project in v9SR2 (because I have it as our previous version still on my machine), reloaded the data, saved the document and then opened it in v10SR3 everything was fine and I can edit the input field now.

[robert99]

Is there a problem with this recommended solution by support

In that if the load order changes then the comment is linked to a different record.

Its a great feature (inputfields) but this solution creates a risk in that its linked to a row (that can change the link to a record) not a record