Calculated Text Color changes to black in Report

[Anonymous]

I have a pivot table where the text colour is calculated depending on its value...the background colour is also calculated.

When the table is put into a report, all of the text is black but the background colours are transferred across.

This is the effect I am after:

The 1's and the 5's that are white here (as they should be)...are black in the report.

Any ideas?  I've been through all the settings I can think of....

[jsingh71]

share any sample qvw then it will easy us to give the solution.

[nizamsha]

its a common problem when u use report for chart object

for simple understanding u may have  u might have select single page.Page-> single page

instead of single page select multipage and  drop ur chart  object it will show ur chart background color

[Anonymous]

Hi,

If I change to multipage, the whole layout messes up!  The table fits on the page...and the background colour is fine, it is just the text colour.

This is how it actually comes out on the report:

How I want it to come out is shown in the orginal post.

My calculations are stored as quite lengthy variables.  I won't post them as they do work...as shown in original post...they are just ignored when put into the report

[nizamsha]

can u post qvw so  i can do it for  u

[nizamsha]

if sorting is the problem in your table use dual in the back end.  what dual actually do is it will display in string but the the values are stored in number  or else post ur qvw with that report only so its easy for us to have a look at it

[#7]

Hi Lauren,

I was having a similar problem with certain red values for text not showing up in reports.

What we found was that the red value in the RGB code has to be below 218.

In your case, the lightest white I can get to show up in reports is: RGB(216,216,216).

Weird glitch.

[Anonymous]

Thanks very much Alexander.  Indeed with 216,216,216 it shows in the report but anything higher and it doesn't.  What a bizarre but highly annoying glitch!!  Lets hope there's a bug fix for this in the pipeline.