Hi @Melvin September! 
The Solid Gauge requires a specific highcharts script that we are not offering currently, and for that reason is not possible. We are exploring solutions to add highcharts scripts the same way you can add add-ons that will allow you to make a gauge chart through extensibility, but we don't have a timeline for that improvement yet.

Hi @Greg Adams!

Yes, to combine different chart types you will need to use the SeriesStyling addon, you can combine any of the available chart types. You can check this sample to see how to do it.

Regarding the Radar Chart, in terms of how to configure it, it's pretty similar to the rest of the charts, just by inputting the data you will have a radar chart with each series being represented as a line. The valuesType property is not mandatory and it's only needed when you want to change the type of data, for example, if instead of categories you want dates on the axis. 
You can find more details on our sample, you can even download the examples to see how they are implemented. If you need a Radar with polygonal axis you can also check this sample that explains how to achieve that use case. 

Try it out and let us know if the documentation was useful :) 

My confusion on radar charts was that I didn't grasp what I was seeing.

To check...

The words that are displayed around the graph are the labels that would usually be displayed on the horizontal axis of a line chart?

So it is like a line graph that has been rolled into a circle?

Yes, the labels around the circle are the ones that are usually on the X Axis, the labels inside the circle represent the values on the Y Axis and each line (the colored ones) represents a Series. 

I installed the new version.

Do I have to do something inside the module to change from using the old one? Set up a new dependency?

The older version seems to have a bug (or I am not using it right) in that a change of color in a line chart only seems to affect the individual points. They are the correct color but the lines connecting them are always blue and the legends under the charts are also shades of blue.

 Is this a known issue/ am I doing something wrong / is it the same in the new version?

you are probably giving the individual datapoints a color.  That is possible (and has its use for making a single datapoint stand out compared to the others in it's series)

But what you probably want is to have a given series in a desired color, you do that by specifying at the series level.  That is true in both old and new version of the charts.

old version is in the advanced format

new version is in addon block

Dorine

Thanks again, Dorine, very helpful.

At the design stage I don't know what the series will be called (1 of 5 possible static names to be selected by user). The color is currently 1 of 7 possible predetermined values but later may be user choice too.

I presume is is possible to put a variable in the relevant boxes instead of the text literals.

In the older version the text variable would have to been generated in the form 

"Color: 'red' "

and for the newer version just

"red"

Does that sound right? 

yes all correct,

that means that in the old version, you'll have to do something like (bold,red,underline for emphasis on the single quotes, what is easily forgotten :

"Color : '" + DesiredColorVariable + "'"

Yesterday I switch the app over to using the V3 charts. Immediate impression was that the default colors for different series are much easier to distinguish one from another than the v1 which used various shades of blue.

Also, very nice to be able to change the type of chart in the properties panel. (Not sure if that was possible on v1)

One odd effect is that when I added a V3 chart next to the original, the original stopped rendering in the browser but still took up space. This wasn't a problem as I was going to delete the v1 charts anyway

Something that confused me is that the new charts have a box where the add-ons are listed. I incorrectly inferred that I was supposed to drag & drop my preferred add-on into this area.

It took a while to see that the properties box already had the add-on boxes.

Copying across the settings from the v1 widgets was easy, although the order of the label and value boxes seems to have switched in v3

Some minor hitches. Having installed V3 via the website I assumed that the widgets would show up in the tool box automatically, but that isn't how things work. I had to 'search other modules.' In the dialog window the old version is marked v1, but the newer version isn't marked with a version.

Having swapped the charts everything worked without any need to change anything.

Also, the use of the very different series colors has removed the need that I was putting off of changing the colors of the series in v1.

(On the link to the samples file, I had no idea what an OPA file was or how to use it. Okay for people who already now, but a mystery to the rest of us. Any chance that a short explanation next to the link could be useful?)

Thank you for the feedback @Greg Adams!

Are you talking about the samples on charts.outsystems.com?
If so, when you click on "Open in Service Studio", opens this popup and at the top you have the link to download the sample with all the working examples:

Once you have it installed in your environment, you just need to input your Server URL and the sample will open on the example you are trying to see.

Hi @MarcosElorza,

Could you please explain what you mean by that?
The Highcharts library is written in javascript so under the hood we use javascript to communicate with it. 
But like the previous version, we provide a low code experience (in this latest version much richer than the previous one) that will allow you to achieve several simple and complex use cases without needing to write a single line of javascript code.
From what you tested what has given you a different perspective so that we can try to better clarify your question?

Cheers,
GM

Hello @Henrique Silva 

Although this is a major version where that could happen, there is only one that you can see in the release notes which was a block that was removed but was already deprecated for a long time. 
You can also check some FAQs present on our landing page here. 

Cheers,
GM

I presume HighCharts itself was upgraded too, so that might result in some broken JSON here and there?

HighCharts is, in general, very downwards compatible, so I wouldn't expect that.

Hi @Dorine Boudry! 

Thank you for the feedback :) 

To answer your points: 

• In this new version we tried to avoid changing the Highcharts defaults because in version 1 we received some feedback that it was not clear which properties we were changing and was difficult to overwrite them. Regardless of that, the reversedStacks property might bring value being offered by default, we will review the decision for this particular property.
  
  
• Regarding the SetHighchartsYAxisConfigs client action, you are doing everything right but since that property it's a boolean, you need to remove the quotation marks. The parameter also accepts false with quotation marks but in uppercase like this: "False". We will also review this to accept it in lowercase.
  
  
• It's an issue and the fix will be included in the next release.

Regarding the structure of the client action, being a list it's the only way we have to allow to reach more than one level of the object. 

For example:
To change the color of the yAxis label you need to use this property, which has 3 levels. So in the client action PropertyPathList you will need the following list:
[0] "labels"
[1] "style"
[2] "color"

If you put just "color" we don't know if it's the color of the axis label, or the crosshair that also has a color property, or other...

I hope this helps!

Best regards,
Jéssica

Ah ok,

 so not for changing the same property on multiple things.

For levels, I just assumed you could use a dot notation, so "labels.style.color", good to know, and maybe good to add that to the description of that structure.

Dorine

Very cool indeed! Thanks for sharing this.

Yes it does, all OutSystems Charts do.