In Development
Last Updated: 29 Sep 2021 12:24 by ADMIN
Scheduled for R3 2021 SP1
Paul Johnson
Created on: 08 Apr 2021 14:21
Type: Bug Report
Selecting a value with no fractional part from a multivalue report parameter of type "float" throws an exception in .NET Core 3.1+ applications
When using a report parameter of type Float, and there is no value for decimal places, or it is 0, it appears as if the parameter value passed to the runtime is converted to an integer value, and an "Invalid value for parameter <paramName>" is logged. 
Posted on: 29 Sep 2021 12:24

Hi Deepak,

One of our developers investigated the bug and right now the fix is in a testing stage. Hopefully, it will be released for the service pack which is scheduled for the 20th of October.

Progress Telerik

Brand new Telerik Reporting course in Virtual Classroom - the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products. Check it out at
Posted on: 22 Sep 2021 20:34
Any thoughts on when this will be fixed?  It's still an issue in R3 2021.
Posted on: 10 May 2021 08:30

Hello Tursunkhuja,

Currently, the status of the Bug report is "Unplanned". Because you have voted for the item, you will receive a notification when there is an update.

Progress Telerik

Тhe web is about to get a bit better! 

The Progress Hack-For-Good Challenge has started. Learn how to enter and make the web a worthier place:

Posted on: 04 May 2021 04:01


What is the status of this bug? We have the same problem and recently asked on Telerik forum: Error when we use parameter type "Float" in Reporting | Telerik Forums