Recently experienced an odd behavior when attempting to alter the color of a cell in a WebI XIr2 report. Selected the cell Properties–Appearrance–>Background Color. When selecting the dropdown for the color pallette, it displays correctly. However when the user selected any color…nothing happened. Now, the interesting thing is that the behavior occurred in a training room for most of the users, not all. No business user outside the room reported the behavior. In a recent test on my browser, I would sometimes have to click multiple times to get the color to select.
Anyone experience the same and resolved it somehow?
Yes I did face this issue but was not able to find the root cause.
I believe it has something to do with the settings on your machine.
I had to manually insert the code to change the colour.
Atleast you were lucky to get the pallette by clicking n times, where in I couldn’t !
It is a machine related issue. I was getting the same error but when I logged in from other machine with same username and password it was working fine.
Can anyone tell me what particular settings on the machine this is related to? I have run into this issue of not being able to click to select the background color on the palette with a handful of machines. I appreciate the workaround tips, but I’d really like to get to the source of the problem, if anyone has figured it out. Thanks.
I had the same problem when I was working with my previous client. With the present customer, there is no such problem. So, i belieive this is got to do something with Monthly Hot Fixes or Fix Packs. Currently, we are using MHF-17
Each colour is associated with a 3 number code i.e. say (255,255,255) for white colour, (0,0,0) for Black color and so on. So, the workaround for this problem what we found out in our previous project is “Type in” these values instead, if you have problems in selecting the color. These values can be typed in the place where the number is already displayed for the present color.
At least one of our users is having the same issue, and she’s on JRE version 1.4.2_03. The funny thing is is that I’m on the same version and I’ve never had the issue. We’re on XI R2 SP3.
We’re afraid to upgrade to a higher JRE version because we’re still running 6.5 and don’t want to run into issues.
Has anyone found the solution or cause of this issue?