Hello, Martin,

Thank you for outlining your user scenario and the need for more advanced configuration options directly within the KendoReact Chart Wizard UI, without relying on custom code.

With the current implementation, the ChartWizard does not yet provide a built-in mechanism for easy customization. While there is no public release date for the features you mentioned and they are not currently on our roadmap, we are constantly striving to improve our components and carefully consider feedback like yours, which is very valuable to us. With this in mind, I’ve gone ahead and converted this ticket into an official feature request and added your vote. We will monitor the interest in the request, please let me know in case further questions arise.

Regards,
Filip
Progress Telerik

Hi, Martin,

The chart wizard leaves bar and column borders undefined, so the chart falls back to the theme default, which is a black outline. With many adjacent bars, those borders dominate visually and make the chart hard to read. We can explicitly set border.width = 0 when rendering bar/column charts:

<ChartSeriesItem
  {...wizardSeriesProps}
  border={{ width: 0 }}   // removes the outline
/>

As for the labels, the wizard doesn’t expose label stepping. But the underlying chart supports it via category axis label step (and optionally rotation / overlap strategies depending on your axis type).I can recommend the following approach:

<ChartCategoryAxis>
  <ChartCategoryAxisItem
    labels={{ step: 2 }}  // show every 2nd label (use 3, 5, 10, etc.)
  />
</ChartCategoryAxis>

As for rendering mixed series types a possible approach I can suggest is to implement a custom component that enables to change the series, I have prepared a runnable example showcasing this approach here:

• https://stackblitz.com/edit/react-bhs4uxtw?file=app%2Fapp.tsx

In case the suggested approaches did not resolve the issues, can you please modify the sample above so that it matches your implementation and the issues are reproduced? This will enable me to debug it locally and find another solution.

Regards,
Filip
Progress Telerik