So, I've spent about a week trying to resolve an issue where we had one sneaky user function annotated with [Function] that worked fine before the change, but when we updated to 19.0.25.211 everything stopped working normally which is documented but I would say this is really a change that users should be made more aware of.
We constantly evaluate the release history paying special attention to "breaking changes" but this is under the category of "improved" and no real indication that it could negatively affect someone's pre-existing reporting should they use [Function] in a way that is now .. changed. Especially when that change causes reporting errors, that are perceived as "broken".
We're already having a hard time justifying the very very fragile nature of using Telerik Reporting (re: vs designer, core vs netframework, the ticket was created in 2018 ...... !!!! Did you know your competitor's vs designer works properly in netcore/netframework??) but this was just so painful. Adding something more to the release notes would have prevented so much wasted time.
1 Answer, 1 is accepted
Hi Kori,
I'm sorry to hear you've had troubles with the user functions loading after upgrading to 2025 Q1. You are right, we should have explained it better in our Release Notes article, and include it in both "What's changed" and "What's improved" sections. Actually the item is placed in "What's improved", because it addresses a feature request logged in our feedback portal here: https://feedback.telerik.com/reporting/1668464
Just to confirm I understand correctly why it does not work on your end:
You have a class containing a few user functions that are used in your reports, but not all of them have the [Function] attribute. Telerik Reporting prior to 2025 Q1 resolved all of the user functions, regardless they have a [Function] attribute or not. But the new behavior only resolves the ones that have the attribute set. In case you remove the attribute from all the functions in the class, the resolution routine should work the old way, i.e. resolve all the user functions. Let me know if this is your scenario please.
As for the Visual Studio Report Designer for .NET projects, I can assure you that we haven't given up and are working to deliver this feature. We know that some of our competitors have this functionality and we understand how important it is to our clients that want to use type report definitions. We will announce any progress in the dedicated feedback item.
Regards,
Ivan Hristov
Progress Telerik
Enjoyed our products? Share your experience on G2 and receive a $25 Amazon gift card for a limited time!