I have a requirement to print a pie chart on a small area. I modified most of the fonts, margins and paddings to make it fit and I got to the connectors. Is there a way to modify the length of connectors?

The problem is that some of the labels are outside of the chart and I was hopping that if I reduce the length of the connectors I can make it fit.

https://dojo.telerik.com/aPuLiPiB

You can see in the above dojo that some categories are outside of the chart area and some are overlaid on the legend

The reason I need to display the chart on that small area is because it needs to be printed and that is the allocated area on the printed paper.

I am using the kendo- scheduler jquery component in my project. Recently I updated the version of the kendo library, I am currently using 

There were customization styles I have done on the component depending on the kendo styling class ex: "k-header", "k-scheduler-navigation", and many more... 

After the update many of my customization styles have lost, Are there any changes done to class names and element types or, element order or any other changes contained in the above update or any later update recently ???? 

Hi,

I have a similar post here https://www.telerik.com/forums/ideas-for-visualisation where we discuss the problem but the crux of the matter is that we want to be able to change the labels on a stacked bar chart after the render process.  Does anyone know if this is possible?

Hi 

We are using a kendo grid with a WCF service to load data in the grid. The grid has sorting, filtering and paging, we are getting 404 error due to long query strings that add the filters for EF behind the scene. These query strings are unmanageable, can you please suggest a way to reduce it and make it work for all clients.

https://xyz.net/DataService/Service.svc/vw_DataPending?$callback=jQuery33105090844870624116_1619444376254&%24inlinecount=allpages&%24format=json&%24top=20&%24orderby=EncounterDate&%24filter=(PracticeLocationsId%20eq%201%20or%20PracticeLocationsId%20eq%204%20or%20PracticeLocationsId%20eq%2016%20or%20PracticeLocationsId%20eq%2020%20or%20PracticeLocationsId%20eq%2025%20or%20PracticeLocationsId%20eq%20111%20or%20PracticeLocationsId%20eq%2092%20or%20PracticeLocationsId%20eq%2010%20or%20PracticeLocationsId%20eq%205%20or%20PracticeLocationsId%20eq%206%20or%20PracticeLocationsId%20eq%207%20or%20PracticeLocationsId%20eq%208%20or%20PracticeLocationsId%20eq%209%20or%20PracticeLocationsId%20eq%2017%20or%20PracticeLocationsId%20eq%2018%20or%20PracticeLocationsId%20eq%2019%20or%20PracticeLocationsId%20eq%2021%20or%20PracticeLocationsId%20eq%2022%20or%20PracticeLocationsId%20eq%2023%20or%20PracticeLocationsId%20eq%2024%20or%20PracticeLocationsId%20eq%2032%20or%20PracticeLocationsId%20eq%2039%20or%20PracticeLocationsId%20eq%2040%20or%20PracticeLocationsId%20eq%20112%20or%20PracticeLocationsId%20eq%2026%20or%20PracticeLocationsId%20eq%2027%20or%20PracticeLocationsId%20eq%2029%20or%20PracticeLocationsId%20eq%2030%20or%20PracticeLocationsId%20eq%20114%20or%20PracticeLocationsId%20eq%2043%20or%20PracticeLocationsId%20eq%2035%20or%20PracticeLocationsId%20eq%2031%20or%20PracticeLocationsId%20eq%2034%20or%20PracticeLocationsId%20eq%2041%20or%20PracticeLocationsId%20eq%2042%20or%20PracticeLocationsId%20eq%2038%20or%20PracticeLocationsId%20eq%20115%20or%20PracticeLocationsId%20eq%2037%20or%20PracticeLocationsId%20eq%2053%20or%20PracticeLocationsId%20eq%2054%20or%20PracticeLocationsId%20eq%2055%20or%20PracticeLocationsId%20eq%2056%20or%20PracticeLocationsId%20eq%2057%20or%20PracticeLocationsId%20eq%20119%20or%20PracticeLocationsId%20eq%2036%20or%20PracticeLocationsId%20eq%2033%20or%20PracticeLocationsId%20eq%20118%20or%20PracticeLocationsId%20eq%2058%20or%20PracticeLocationsId%20eq%2059%20or%20PracticeLocationsId%20eq%20113%20or%20PracticeLocationsId%20eq%20116%20or%20PracticeLocationsId%20eq%20120%20or%20PracticeLocationsId%20eq%20121%20or%20PracticeLocationsId%20eq%2060%20or%20PracticeLocationsId%20eq%2062%20or%20PracticeLocationsId%20eq%2063%20or%20PracticeLocationsId%20eq%2067%20or%20PracticeLocationsId%20eq%2083%20or%20PracticeLocationsId%20eq%2084%20or%20PracticeLocationsId%20eq%2074%20or%20PracticeLocationsId%20eq%2073%20or%20PracticeLocationsId%20eq%2070%20or%20PracticeLocationsId%20eq%2069%20or%20PracticeLocationsId%20eq%2064%20or%20PracticeLocationsId%20eq%2065%20or%20PracticeLocationsId%20eq%2066%20or%20PracticeLocationsId%20eq%2072%20or%20PracticeLocationsId%20eq%2068%20or%20PracticeLocationsId%20eq%2075%20or%20PracticeLocationsId%20eq%2081%20or%20PracticeLocationsId%20eq%2093%20or%20PracticeLocationsId%20eq%2061%20or%20PracticeLocationsId%20eq%2076%20or%20PracticeLocationsId%20eq%2077%20or%20PracticeLocationsId%20eq%2078%20or%20PracticeLocationsId%20eq%2079%20or%20PracticeLocationsId%20eq%2080%20or%20PracticeLocationsId%20eq%2082%20or%20PracticeLocationsId%20eq%2085%20or%20PracticeLocationsId%20eq%2086%20or%20PracticeLocationsId%20eq%2087%20or%20PracticeLocationsId%20eq%2094%20or%20PracticeLocationsId%20eq%2095%20or%20PracticeLocationsId%20eq%2096%20or%20PracticeLocationsId%20eq%2098%20or%20PracticeLocationsId%20eq%20100%20or%20PracticeLocationsId%20eq%2099%20or%20PracticeLocationsId%20eq%20101%20or%20PracticeLocationsId%20eq%20102%20or%20PracticeLocationsId%20eq%20103%20or%20PracticeLocationsId%20eq%20104%20or%20PracticeLocationsId%20eq%20105%20or%20PracticeLocationsId%20eq%20106%20or%20PracticeLocationsId%20eq%20107%20or%20PracticeLocationsId%20eq%20108%20or%20PracticeLocationsId%20eq%20109%20or%20PracticeLocationsId%20eq%20110%20or%20PracticeLocationsId%20eq%2089%20or%20PracticeLocationsId%20eq%2088%20or%20PracticeLocationsId%20eq%2090%20or%20PracticeLocationsId%20eq%2091%20or%20PracticeLocationsId%20eq%20123%20or%20PracticeLocationsId%20eq%20124%20or%20PracticeLocationsId%20eq%20125%20or%20PracticeLocationsId%20eq%20126%20or%20PracticeLocationsId%20eq%20128%20or%20PracticeLocationsId%20eq%20129)

I have a client who requested when a kendo control can't validate, the focus is kept on the invalidate object.
This is something that to my knowledge isn't supported by default by the components.

So i've tried something like writing a validation rule like this (raw example, won't work)

rule :function(input){
    var isValid = false;
     //some code to do validation
     if(!isValid){
        var kendoComponent = $(input.id).data("kendoCombobox");
        input.focus();
    }
    return isValid
}

The problem i'm having is that before input.focus(), the next component shortly ahs focus, and by setting the focus to the invalidate compinent, the next components validation is triggered as well. The next component says it's invalid, and thus calls for the focus. Creating an endless loop between these 2 components each asking for focus.

To try and counter this, i've kept a dominantfield status. If the validation is triggerd for a none dominant component, that component should always say "i'm valid" thus not calling for focus. As far is i can determine following stacktraces and output logging, this code is working, though somewhere focus is still being called on the second component causing an infinite loop. while the custom code i wrote in my validation ruls never call .focus() on the second component. I can't figure out why the components would still keep trying to get focus. or why in the telerik js code, an infite loop would be created.

Any thoughts on why this infinte loop could be created, or any input as how else this functionality can be obtained?

Hello, when did the SearchPanel "search" command become a built in command for the grid toolbar:

https://docs.telerik.com/kendo-ui/api/javascript/ui/grid/configuration/toolbar

I'm using a 3rd party tool that uses kendo.version: 2018.3.1219

When I pass in the "search" command, it just creates a search button, does not create the search box:

Was that search panel built into the library during a later release?

DataSource

transport: {
read: {
url: crudServiceBaseUrl + "?r=panel/json",
contentType: "application/json",
dataType: "json",
type: "GET"
},

...

parameterMap: function (options, operation) {
if (operation !== "read" && options.models) {
return {models: kendo.stringify(options.models)};
}
return kendo.data.transports["odata"].parameterMap(options, operation);
}

...

schema: {
model: {
fields: {

....

date_begin: {
type: "date",
parse: function (value) {
return kendo.toString(new Date(parseInt(value * 1000)), 'yyyy-MM-dd HH:mm:ss');
},
validation: {required: true}
},

....

columns

field

{
field: "date_begin",
width: "120px",
title: "Date Begin",
},

... after update grid 

update: {
url: crudServiceBaseUrl + "?r=panel/update",
dataType: "jsonp"
},

it is show me 

53291-12-11 17:50:00

i don't know why

any help?

Hi, 

I have a few issues the Scheduler control as follows:

Problem 1

When I try to import calendar event using the demo application https://demos.telerik.com/kendo-ui/scheduler/import-export-ical  with uk bankholiday I download from https://www.calendarlabs.com/ical-calendar/holidays/uk-holidays-75/  but I get a javascript error as follows, It looks like the DTSTART:20200101 does not have a time stamp,  It would be nice if the control could validate when importing and report this to the user, I can also replicate the problem by removing the timestamp from the default data provided in the demo site, I know its a data issue but is there a workaround?

ical.min.js:1 Uncaught Error: invalid date-time value: "2020-01-01T::"

I am trying to do a simple test where a button click hides the first column of a grid.  Unfortunately, there is a JavaScript error in the Kendo UI layer (2019.2.619) when my call happens.  Is there some easy way to fix this?         

The error:
Uncaught TypeError: Cannot read property 'style' of undefined

    at init.hideColumn (kendo.all.js:65537)
    at HTMLButtonElement.onclick (CustomerCode:312)

Hi, I’m wondering if you guys would have any ideas on what would be a good approach to representing data that highlights the condition of items over time but where the ‘health’ of each item in the series dictates it’s position in the visualisation.

It’s quite hard to explain but I’ll try…

If we were alanysing the radiation exposure of planets over time we could give them a score 1=OK (green), 2=Warning (amber), 3=Critical(red).

If for January Mars was critical it would appear first in the visualisation and red in colour. If in February it’s exposure changed to OK and Venus was critical, Venus would appear first and red with Mars later in the series and green.  So, each planet has a Red-Amber-Green (RAG) score for the condition it's being measured against.

We’ve been attempting to model this using a stacked bar but have got to a point where we think using another approach rather than trying to make a chart do something it’s not designed for might be a better appoach. Specifically we are having an issue making each series render in order of it's RAG. There would be multiple ‘charts’ on the page for different conditions, say, radiation, solar wind speed, spin velocity (making things up here!)…

Do you have any ideas / suggestions on an approach - such as which chart might be good starting point - more than happy to receive any ideas on alternate visualisations. Here’s an example of one chart we’ve been working towards where I've edited the HTML to make it look like it works (in reality we can't get the order of planets to present in a different order (for each date range) whilst maintaining the red at the left, green at the right visualisation.