Pie Chart Errors, Does Not Display

Hi Kerry,

I tested both the provided code and the sample from the linked article and the charts are displayed successfully at my end. Can you, please, share some more details on the exact environment in which the issue occurs? Does it happen in all browsers or only in a specific one? If it is IE, can you check whether it is not running in Compatibility mode?

It will be really helpful if you send us a runnable sample (including the usd web.config configurations) so we can replicate and examine the cause for the problem further.

Regards,
Vessy
Progress Telerik

Have the same problem.

It was working in 2016_3_1027 and is broken in 2017_1_228. Version 2017_1_118 is not tested.

All I know it has something to do with LabelsAppearance on PieSeries. Can't isolate the problem, but seems that it is not related to data.

Setting LabelsAppearance.Visible = false fixes problem, but labels are hidden, so it is just temporary workaround to keep chart running.

Just FYI

2017_1_118 - Works fine

2017_1_228 - Is broken

I found that version 228 contains a new version of Kendo components (html5.dataviz.chart etc.), so maybe you changed something inside?

And last thing, calling this code from Immediate Window in my page (just init part from rendered page) throws "Unable to get property 'labels' of undefined or null reference"

Not the best runnable sample, but that's all I can get. You can test it on your own, just change client id of control to any existing.

$create(Telerik.Web.UI.RadHtmlChart,
{
    "_chartArea": "{background: 'transparent'}",
    "_chartTitle": "{visible: true,font: 'bold 16px Arial,Helvetica,sans-serif',margin:20}",
    "_clientEvents":
    {
    },
    "_dataSource": "[{\"Name\":\"Pro zobrazení grafu musí být vybrán jeden hodnotící parametr !\",\"Value\":1,\"DefaultColor\":\"#4F81BD\",\"_Percentage\":100,\"_Value\":\"1\"}]",
    "_layout": "default",
    "_legend": "{visible: false,labels: {font: '12px Arial,Helvetica,sans-serif'}}",
    "_pannable": false,
    "_plotArea": "{appearance: {background:'transparent'},tooltip: {visible: true}}",
    "_series": "[{type:'pie',field: 'Value',name: 'Název',tooltip: {visible: true, template: '<div style=\"text-align: right\"><strong>#=dataItem.Name#</strong><br/>#=dataItem._Value#<br/><em>#=dataItem._Percentage#%</em></div>'},colorField: 'DefaultColor',type: 'pie', startAngle: 0,colorField: 'DefaultColor',categoryField: 'Name',labels: {visible: true,font: '12px Arial,Helvetica,sans-serif',template: '#=dataItem.Name#: #=dataItem._Value# (#=dataItem._Percentage#%)'}}]",
    "_uniqueId": "ctl00$Telo$Dock_1353$C$ctl00$bc",
    "_zoomable": false,
    "clientStateFieldID": "ctl00_MainContent_RadHtmlChart1_ClientState",
    "skin": "CMS_Black"
}, null, null, $get("ctl00_MainContent_RadHtmlChart1"));

Hi Raptor,

I tested the Pie chart with the mentioned versions (as well as with the latest 2017 Q2 SP2 release) but still no errors are thrown on my end. I am attaching my test page to this reply - are you able to reproduce the issue with it? If no, can you try to modify it up to a point where the issue occurs and send it back for a further investigation?

Thank you in advance for your cooperation.

Regards,
Vessy
Progress Telerik

Hello,

simple Pie chart in page works fine. Must be related to Ajax panels or something else. It is hard for me to create sample, it crashes in out CMS and it is no easy to separate result.

 

R.

Well, last attempt form me. Tracked down this and it throws exception in html5.dataviz.chart.js on code

"var themeLabels = chartService.theme.seriesDefaults.labels;"

in PieSegment.render() function.

There is no "theme", so seriesDefaults and labels ale undefined.

Maybe it can help you to track changes in dataviz what exactly causes this error. I think I can't do more :-(

Ok, got it :-)

Problem is only when you are using custom skins. We have our own skin for Telerik Asp controls. When creating Kendo widget in PieChart, there is function:

            _getThemeOptions: function (userOptions) {
                var themeName = (userOptions || {}).theme;
                if (defined(themeName)) {
                    var themes = dataviz.ui.themes || {};
                    var theme = themes[themeName] || themes[themeName.toLowerCase()] || {};
                    return theme.chart || {};
                }
            }

But there is no custom skin included in themes, so it returns {} as theme. And then it crashes as I wrote in previous post.

You can simply test it including any custom skin in project and changing global settings in web.config.

        <add key="Telerik.Skin" value="CMS_Black"/>

It results to error.

Please test it on your side and let me know . Thnx.

Excellent find, Raptor! We are also using a custom skin for our Telerik controls, all contained within a DNN (CRM) site.

Hi guys,

Thanks, Raptor, for sharing your findings with us. I have logged the reported regression bug and we will do our best to have it fixed as soon as possible. You can track its progress here:
https://feedback.telerik.com/Project/108/Feedback/Details/226354

I have also increased your Telerik points a bit as a small token of gratitude for your report.

Regards,
Vessy
Progress Telerik

Hi,

is this problem fixed in R3 2017?

Hello Kerry,

I am afraid that the linked bug is not fixed for our 2017 R3 release. The status of the item will be updated immediately when the issue is resolved, so you an subscribed to get updates for it.

Regards,
Vessy
Progress Telerik

Hello,

when it will be fixed? It takes so long, customers are not happy.

Hi Raptor,

The bug is planned for fixing for our next Service pack and if everything goes well with the backlog (no critical issues with higher priority appear) the fix will be included in our next release. The status of its feedback item will be updated immediately when the bug is handled:
https://feedback.telerik.com/Project/108/Feedback/Details/226354

Please, accept our apologies for any inconveniences this is causing to your work.

Regards,
Vessy
Progress Telerik

Hi,

a new major version is out and bug feedback item is still untouched. Where is the problem? You doesn't care about reported bugs anymore?

Raptor

No need to be rude, Raptor.

Yes, you are right, sorry.

I just don't understand how can this take so long to fix. In service pack, not fixed. In next major release, not fixed.

I'm just disappointed, that's all.

Hi guys,

The main focus in our latest releases was applying of some important security improvements, thus many of the logged bug fixes were postponed in favour of these security changes. We do work on fixing and improving the controls and do our best to resolve as much issues as possible, looking at them on priority base. I have increased the priority of this item to the highest level, so it will appear on the top of our backlog now. 

Please, accept our appologies for the caused inconvenienses, we will try to fix this as soon as possible. 

Regards,
Vessy
Progress Telerik

Hi guys,

We are currently working on the bug discussed in this thread and it seems to be not reproducible with the latest release. I am attaching my test project to this reply - can you, please, confirm that the chart is running without any on your side as well?

Please, make sure as well that all settings required for the chart new skin creation described in the following article are applied on your side:
https://docs.telerik.com/devtools/aspnet-ajax/controls/htmlchart/appearance-and-styling/create-custom-skin

Regards,
Vessy
Progress Telerik

Hello,

may I ask you in what version it should be fixed? 2018_1_117?

Well, problem is, that HtmlChart is Kendo control inside ASP.Net pack. Theme in this case is not "theme", it is just JSON definition. It should be style, to be the right theme. But ok, I understand it. It is JavaScript control, so ok.

But there is other problem. We don't want to create JSON definition of skin. BTW we are leaving custom skins because of hard maintenance in new versions. But there should be internal mechanism that checks if custom skin name definition exists or not. Then it should do fallback to default skin. It is JavaScript, so it is easy to test. There is no need to define another Theme. Exists? Use it. Undefined? Use default.

 

Regards

Raptor

Hi Raptor,

Thanks a lot for the shared feedback. I have passed your suggestion to our Product Manager and he aggeed to implement Default-skin fallback of the control whenever the set custom skin is undefined. This change is applied and is set for testing now - if all other functionality of the control is working smoothly with this change it will be included in our next release.

In addition, I have updated your Telerik points as a small token of grattitude for your feedbck.

Regards,
Vessy
Progress Telerik