If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Prompt page not displaying properly in IE8

Started by midhl, 09 Aug 2011 11:42:15 PM

Previous topic - Next topic

midhl

Hi,

We have an issue where a report prompt page (has Java Script used in it) when run in IE 6 is working fine but when the report is run in IE8 prompt page is not aligned properly and some prompts are not even visible. Strangely when the same is run for the second time in IE8 it was looking fine. Client is looking for some sort of fix. Not clear what the issue is. Any of you guys have faced any such issues or any ideas on what might be causing such an issue and how to resolve. Currently we are using Cognos 8.4


Thanks in advance.

blom0344

IE 8 is supported from 8.4.1. onwards  (not 8.4!!), so you may try to upgrade..

midhl

Thanks for your reply and will take your suggestion

midhl

Hi,
Although it appears to be IE issue(Cognos 8.4 doesn't support IE8), Client is not willing to accept our version since rest of almost 150 reports have Java Script in the prompt page and are working fine .Its only with this report the prompt page is not displaying properly in the first run. When the report is run again its working fine. But when the cache,temp files and cookies are deleted from the browser logged out of Cognos and when logged in again and the report is run prompt is not displaying properly.
Any ideas on what could be done to overcome this.
Thanks in advance

blom0344

Use the URL with IE 7 compatibility mode?

bdbits

It seems to me that if your other reports are working fine, the problem likely lies with the Javascript on this specific page. A possible scenario that occurred to me is that maybe the Javascript is looking for a cookie. When it does not find it, creates the cookie but does not set a local variable with the default, causing the problem. When the javascript comes around the 2nd time, it finds the cookie and sets the local variable with the default value as expected.