Skip to main content
Announcements
Live today at 11 AM ET. Get your questions about Qlik Connect answered, or just listen in. SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
m_baroja
Partner - Contributor III
Partner - Contributor III

INPUTFIELD wrongly displayed in server

Hello,

We are facing a somehow enigmatic issue.

We want a field displayed and followed by the same value but as INPUTFIELD, so that it can be changed. Something like this:

INPUTFIELD X;

INPUTFIELD Y;

INPUTFIELD Z;

Table:

Load B,

        C,

        D,

        D as X,

        E,

        E as Y,

        F,

        F as Z

Resident FirstTable;

When we load this fields and display them in Desktop (both in client and in server), they are both the same value as expected. But when displayed through Access Point, the values are mismatched!! INPUTFIELD field doesn't show the same value as the original field but another different value, which is a real value from that field, but not the identical one, as shown in the attached pictures.

Any ideas??

Thanks!

1 Solution

Accepted Solutions
m_baroja
Partner - Contributor III
Partner - Contributor III
Author

This seems to be a bug in the version we were working with. After upgrading to QV 11.20 SP15, it's solved.

View solution in original post

3 Replies
settu_periasamy
Master III
Master III

Hi Miguel,

Not able to find the proper difference from your screen shot. both images showing different order.

Can you post the exact images (without scroll in the chart ) from your desktop and accesspoint with proper order? or Can you provide the sample file?

m_baroja
Partner - Contributor III
Partner - Contributor III
Author

Here you are.

As you can see, the Desktop image shows everything correct, but when shown in AccessPoint, INPUTFIELD values are not the assigned ones, but some other values corresponding to another "Almacen".

In this images we have filtered the results, but the same happens without filtering them.Desktop (1).pngAccessPoint (1).png

m_baroja
Partner - Contributor III
Partner - Contributor III
Author

This seems to be a bug in the version we were working with. After upgrading to QV 11.20 SP15, it's solved.