Axis Range maximum

[dougp]

Cognos 10.2.1                                                           
Windows server 2012 R2                                                 
Windows 7                                                               
IE 11                                                                   
Report Studio                                                           
                                                                       
For a chart, setting the axis range maximum value for the y-axis to a specific value does not work.  If the values in the chart exceed the user-selected value, the chart y-axis behaves as if this property is set to automatic.  See the attached report spec for an example from the GO Sales (query) package.

Here's a scenario:
I have monthly values that mostly range from 25 to 35, but I have one exception that is 90.  I don't want to filter out the 90 because it's valid data.  Readers of the report understand what that one value means and that its actual magnitude is not very important.  It is acceptable for the top of that bar to disappear off the top of the chart.  What they want to see is more prominent differences between the other values.  If I were to set the axis range maximum for the y-axis to manual and choose a value of 200, the graph would scale correctly.  If I set the value to 40, Cognos will see that the values in the graph exceed my manually set limit and will ignore the manual setting and revert to automatically calculating the y-axis range maximum.

Has anyone else seen this?  Is there a workaround?

Go Sales (query) package.

[BigChris]

I've never found a workaround...I've always just treated it as "one of those things". The scenario where it usually happens for me is with percentages on the y-axis and the measure hits 100%. It doesn't matter if I set the maximum on the axis, it still seems to put the next interval on the axis for me (grrrr...)

[Lynn]

Have you played around with adding another axis to the chart? Not sure if it will work in your situation but if you can identify the exception and bucket it separately from the normal items you can put it on a secondary axis.

[dougp]

IBM Support told me that this is a known issue and there is an APAR to get it fixed.  They also provided a workaround that the support person said didn't work for him, but it worked for me.

http://www-01.ibm.com/support/docview.wss?uid=swg21628552