Value Range settings in Combination Chart Visualization

[Lynn]

I posted this question on the Rave board but I'm not sure if there is as much viewership as this one so please forgive this repeated post. It is still a reporting question, just pertaining to use of a visualisation.

In a nutshell, the axis range settings for the combination chart viz are ignored for both the primary and secondary axis no matter what values I specify. I may try to post a bug but am hoping someone might confirm the issue or else point me towards what I am doing wrong.

Attached is a spec where I've replicated the issue using the GO Sales (query) package. My situation is also against a relational package, although I'm not sure that matters in this instance.

If you run the report you'll see a list of what the underlying query returns: quantity and unit price by year for 2010 through 2013. The chart beneath is a combination chart from the samples available from IBM. I have quantity on the primary axis and unit price on the secondary axis. Note that the unit prices are all between $120 and $130, but the axis (by default) includes zero so the line is rather flat at the top of the chart.

I'd like to simply exclude the 0 (which works fine in other chart types) to distribute the line more. If I untick the option to exclude zero the chart is exactly the same. If I set an explicit range there is also no change. I tried this on the primary axis as well and find the same problem (although in my case it is really the secondary axis that I want to affect.

Of course the standard combination chart (rather than the visualisation) works fine, but this is ultimately for an Active Report so I need to use a viz.

Thanks in advance if anyone has a moment to give it a try.
Lynn

[MFGF]

I posted this question on the Rave board but I'm not sure if there is as much viewership as this one so please forgive this repeated post. It is still a reporting question, just pertaining to use of a visualisation.

In a nutshell, the axis range settings for the combination chart viz are ignored for both the primary and secondary axis no matter what values I specify. I may try to post a bug but am hoping someone might confirm the issue or else point me towards what I am doing wrong.

Attached is a spec where I've replicated the issue using the GO Sales (query) package. My situation is also against a relational package, although I'm not sure that matters in this instance.

If you run the report you'll see a list of what the underlying query returns: quantity and unit price by year for 2010 through 2013. The chart beneath is a combination chart from the samples available from IBM. I have quantity on the primary axis and unit price on the secondary axis. Note that the unit prices are all between $120 and $130, but the axis (by default) includes zero so the line is rather flat at the top of the chart.

I'd like to simply exclude the 0 (which works fine in other chart types) to distribute the line more. If I untick the option to exclude zero the chart is exactly the same. If I set an explicit range there is also no change. I tried this on the primary axis as well and find the same problem (although in my case it is really the secondary axis that I want to affect.

Of course the standard combination chart (rather than the visualisation) works fine, but this is ultimately for an Active Report so I need to use a viz.

Thanks in advance if anyone has a moment to give it a try.
Lynn

Hi Lynn,

I didn't have the visualization you are using installed, so I switched it to the az.combination visualization from AnalyticsZone.

My experiments with it work fine:



There are two places you can set the axis ranges - in the properties of the main visualization, and in the properties of each of the two measures. I ended up putting minimum values into the properties of the visualization, and minimum and maximum values into the properties of each measure.

My report spec is below - see if it works the same for you.

Cheers!

MF.

[Lynn]

Thank you!!!

The other one did not have the option to set min or max on the main visualisation property page. I did try the az version also but missed the main properties on there.

I do notice that if I don't set a specified range on the metric itself (instead just select all data but exclude zero) it chops the range at the very top, but I can live with that. In an active report situation it is difficult to find a max value that works for all possible filter scenarios.

Thanks very much and have a safe trip this afternoon!