Shared scales in line chart, combination chart and bar chart

The new functionality in 10.9 is great - easy to use and migrate existing charts to using dual scales.

You took your time on this one TIBCO but for me the results are perfect!

It is really good to have this functionality -and a lot more- in a version prior to the next LTS so we can all test this and give feedback here and via TIBCO's and PerkinElmer's support (https://informatics.perkinelmer.com/Support/Contact/) for the LifeScience community. Please share your feedback and don't hold back. It is really good information and it can't be more timely.

Some progress in 10.9

"Dual shared scales Spotfire visualizations that support multiple scales now also support shared dual scales. This means that you can create visualizations that display, for instance, 5 pressure values and 3 temperature values, using just two scales; one for pressure and one for temperature. This is available in the bar chart, line chart, combination chart, and scatter plot.

Choose right or left scale position You can now select the scale position for visualizations that use just one scale. You can position the scale on the right or left side."

Need to check out the behavior but looks useful so far.

Just a small note to everyone who is bashing Tibco for not being able to implement this for 4 years now: 4 years is only when the Ideas portal was created, and Tobias bulk imported all the previously raised pending Feature Requets from their previous method of tracking into this new site. So it is more than 4 years :) (to put it into context, less than 3 years was the difference between the initial release date of win8 and win10)

I agree with previous comments about how this seems to have be ignored in favour of other more minor changes.

If the issue is one of trying to maintain comparability with the existing charts, why not do what was done when the map charts were changed- create a new visualisation type that co exists alongside the current one for a period of time?

That way users can build new visualisations that use the new features and migrate older visuals to the new one themselves over time

And still no addressment from the product owner on where on the prioritization train this issue was,is, will be. Actually, they may not even have this on their development train. I hear this feature would touch many locals of the base code, but not much else.

Hi Niklas,

The comments would make much more sense if the product was getting more features rather than rearranging the menus and the TABS. Do you realize how many analysis instructions and usability complaints we got as a result of the 10.x deployment when this HARD change was introduced.

What IDEA request # was voted so high to put the page tabs at the bottom and increase the complexity to work with data tables. Who did the user experience and deployment impact testing testing on this one issue????

When was the last time a new visualization interaction feature was introduced?

The visualizations are what people see, and that's not changing. It really has now got to a point of resentment.

We are aware of the importance of this request, and understand that it is frustrating and may seem strange from the outside that we don't immediately address this and other long standing commonly requested features. Your input is very important to us. We review all new ideas, read every comment and frequently review top voted items to see how we can fit them into our development plans.

Unfortunately it is not possible for us to address all top requests - at least not right away. Reasons include:

- We are trying to strike a balance between transformational improvements like adding streaming data capabilities and polishing existing features like how the scales work in our visualizations.

- Sometimes, while a feature request may seem small and easy to fix, we may need to first make a bigger change to make it possible to address the request, or to solve multiple requests in a more effective way.

- When we add to an existing feature (like adding a new scaling option to an existing visualization) we also need to make sure that everything else works as expected when used together with the new capability. Since Spotfire is extremely interactive and responsive (The data can change at any time and the user can change the visualization at any time) this is sometimes quite complicated.

Thank you.

Niklas Amberntsson

Senior Product Manager

You really need someone dedicated to customer feedback. This is far away from being professional.

Wow we are going on 4 years now.

So many years already.... Still no solution? So many other charting tools have done it and it is basic for them. I wonder why my company is still paying license money for this tool.

Please implement ASAP.

The ability to have comparable figures on the same scale axis vs a % trend on the opposite is a fairly basic business requirement we need.

Thank you for your time.

Hi Team,

I've filed an Idea to represent multiple scales by color to be used in the combination chart with stacked bars and explain more about our own scenario.

Here is the Idea number: TS-I-7387. Please merge it to this one if its discussing the same topic.

Best Regards,

Ghannam

Yes, would like to see the ability of left/right scales to have a single scale on each side. This is useful when graphing multiple variables with 2 different units. Requirement is for all variables on one axis to fall withing the same scale (max to min) and not to default to each individual scale range.  Manually setting the Max value for all variables in the properties doesn't work very well when there is a large variance in the underlying data which changes with filtering.

Thanks for the update Brad, looking forward to seeing what Tibco come up with for this. As is always the case with data analytics or software engineering, everything is always more complex than it looks from the outside! 

Hello all of you dedicated fans of this "shared scales" idea! This is Brad Hopper, I'm the VP of Product Strategy for TIBCO's analytics portfolio, including Spotfire. I wanted to respond to this thread to let you know that we are very aware of the strong desire for this capability in the product and have been doing research on what it will take to deliver a solution. As you can see the idea is market as "Under Consideration". We don't do that unless we are in fact looking into design considerations, engineering estimates, surrounding requirements etc. and investigating timing and prioritization. At the top of the thread you can also see that this idea has 11 merged ideas - as it turns out, there are a lot of considerations about this one that make it more challenging than it appears, although I'll admit it seems quite straightforward it touches several places in the codebase (and there are other work items we might like to combine with it) so there is more work to be done here. When we can share more we will, but in the meantime, don't hesitate to describe other cases in which shared scales will be useful for you, we are listening and taking notes. Thanks for your passion! - Brad

Not addressing this thread is bad business Tibco

Any news on that? More than three years already for such a basic functionality. 

I support the capability described above to be implemented ASAP.

I developed a workaround (I wouldn't call it a solution) that has proven helpful for addressing the need for a dual y axis with proper labels and shared grid lines. It relies on python scripts that look at the ranges needed for each axis and compromise on a good set of min and max values on either side that are nicely divided by 2,3,4 or 5 so that the grid lines end up with round numbers. I've shared this approach with Tibco and they've discussed building the functionality into the Combo Chart but I haven't heard any updates on that front for quite some time. Some typical charts are attached to demonstrate the end-result (notice the well-chosen axis labels on BOTH y axes).

If anyone's interested in this approach, let me know and I could share the scripting details.  (paul_jones@keysight.com).