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: 
Not applicable

error message shown at the top of chart.

@Hi,

Can anyone help me in positioning the calculation condition message at correct position. It should be always at the center of the chart.

When I view the chart in web view, the error message moves to the top of the chart. I used chr(10) to make it to the center. Do you have any better idea?

Attached is the screenshot for the problem.

9 Replies
sudeepkm
Specialist III
Specialist III

I tried it in web view and was able to see the error message in the middle. Please see the image below.

Can you please tell me the QV version and IE version in your system?

T115312.png

Not applicable
Author

In QlikView it displays in the same way like error message on top in Web View.

There is no option available to change its position.

Not applicable
Author

I am using QV v11.2 SR3

v_iyyappan
Specialist
Specialist

Hi,

I have also same position in error message. Qlikview 11 and IE 8.0

Alternative Method is there. When you get calculation condition failed show the text object in center position error message text.

Regards,

sujeetsingh
Master III
Master III

i think there is no specific option of Error msg layout setting what you can do is that have a text Object with conditional enabling and it get enabled at the required position you want

Not applicable
Author

Using a text object with a conditional show is the easy way

Not applicable
Author

Thanks Iyyappan V But I want to set the position of error message itself instead of using other ways.

Not applicable
Author

Without editing the XML of the object I cannot see how u would do it .... sadly im installing QV atm so cant test

ergustafsson
Partner - Specialist
Partner - Specialist

Hi Deepak,

Can you try this out in the latest version, both for QV 11.20 and for your browser? It would be good to confirm the issue does not exist in the latest version.

Regards,

Erik