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

Announcements
Join us in Toronto Sept 9th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Input box enable expression is not working using IE

Hi,

I have developped a QlikView dashboard with input box. The functionality is for the user to enter coma separated text in the input and which will be applied to the current selection by a macro. It is working perfectly on development box.

When we deploy this on server and users accessing this using IE is having issues. When users click on '...' symbol next to the input box value, no expression window is coming. This is preventing user to edit long text which is in input box. I have enabled the 'Enable Edit Expression' property of the input box.

Is any one know is there any special settings that needs to be done to enable this?

Regards,

Murali

7 Replies
Miguel_Angel_Baeyens

Hi Murali,

I've just tested a simple input box in QVS 10 SR3 build 9061 and it's working as expected, using the plugin (same version than Server) with port 4747 open (using the QVP protocol) and browsing with IE 8. I had indeed checked the "Enable Edit Expression". Is it possible that the window is somewhere in the background so you don't see it or is it considered as a popup by your browser so you can see it either?

What version of IE are you using?

Hope that helps.

Miguel Angel Baeyens

BI Consultant

Comex Grupo Ibérica

Not applicable
Author

Hi Miguel,

I clicked on 'Restore settings' in internet options. That worked for a while.

When I close and open the browser, it stopped working.

Is there any reason for this?

Regards,

Murali

Miguel_Angel_Baeyens

Murali,

There may be some domain policies that are affecting your browser? Does that happen in every computer?

Regards.

Miguel Angel Baeyens

BI Consultant

Comex Grupo Ibérica

Not applicable
Author

Yes. This happens on few PC's that I have access to.

But what I am looking for is to identify what is that property that is causing this problem, so that I can request the network team to handle it from domain policy level.

Thanks a lot for all your help till now...

Not applicable
Author

I am having the same issue, have you filed this as a bug?

Not applicable
Author

I have "discovered" that this object is very senstive to the sheet it is on in my document. When I moved it to another sheet it works just fine in both developement and on the server.

Not applicable
Author

I have "discovered" that this object is very senstive to the sheet it is on in my document. When I moved it to another sheet it works just fine in both developement and on the server.