This is a migrated thread and some comments may be shown as answers.

Using library functions in report's expressions

3 Answers 127 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Daniel
Top achievements
Rank 1
Daniel asked on 05 Aug 2008, 12:32 PM
We can use UserFunctions in reports, which is static function defined on same report if I understand it correctly. Now what if I want to use same function that is in some library class in more then one report?

Also, have you considered allowing use of instance members of report?

Thx in advance.

Daniel

3 Answers, 1 is accepted

Sort by
0
Svetoslav
Telerik team
answered on 06 Aug 2008, 08:51 AM
Hi Daniel,

Currently you are allowed to use only static methods which as you may have already noticed is some kind restrictive. Anyway we have still a lot of work on the expressions and we will definitely have your suggestions in mind when working on the future versions.

All the best,
Svetoslav
the Telerik team

Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Daniel
Top achievements
Rank 1
answered on 04 Jan 2009, 11:30 AM
Half year passed and there is still no support for glabal user functions as I understand it. I was thinking I'll overcome it by making my own report class inheritted from Telerik.Reporting.Report and define commonly used functions/properties there as static ones so I can use them in all the reports (I have hundreds of reports). But this doesn't work either. Can you provide us some kind of solution for this and some more clearly defined schedule when you plan to improve this?

Best regards,
Daniel
0
Svetoslav
Telerik team
answered on 08 Jan 2009, 10:39 AM
Hi Daniel,

We do understand that the current implementation of the user functions is not good enough and have already scheduled it for improvement in for the 2009.1 version of Telerik Reporting expected by the end of February.

Since the expression engine looks for user function only at the current report level you should always define them as public static members of your reports. A possible workaround is to use proxy functions in your reports that call the actual function.

Best wishes,
Svetoslav
the Telerik team

Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Tags
General Discussions
Asked by
Daniel
Top achievements
Rank 1
Answers by
Svetoslav
Telerik team
Daniel
Top achievements
Rank 1
Share this question
or