Hi,
Is there an event run when the user clicks on the Action of a report E.G
Drill report Liks to a Sub report.
When user clicks to load this report Fire Event user wants to load X Report..
What i would love would be an action to "run action even", so that when a user clicks a code on the report we cold load a code edit window in our main app.
Is there an event run when the user clicks on the Action of a report E.G
Drill report Liks to a Sub report.
When user clicks to load this report Fire Event user wants to load X Report..
What i would love would be an action to "run action even", so that when a user clicks a code on the report we cold load a code edit window in our main app.
4 Answers, 1 is accepted
0
Accepted
Hello David ,
Peter
the Telerik team
Thank you for your suggestion. Introducing some kind of hook ups to handle custom actions is already in our TODO list and this feature will be implemented for a subsequent version of Telerik Reporting. Once we have a clear view on its implementation we would update the product's roadmap.
All the best,Peter
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0
Travis
Top achievements
Rank 1
Rank 1
answered on 18 Apr 2011, 10:40 PM
Was this ever implemented in the latest release?
0
Hi Travis,
If we get back to this request and try to understand your particular scenarios, you most likely have a report that contains some kind of "commands" for your application that are not valid from outside the application, is that correct? Although we're not familiar with your application we would suggest extracting these actions from the reports to the application. This way the reports will contain only relevant information and will be really portable - that is you can export them to PDF or Excel and can open them outside your application.
That said the question that is bothering us is not technical but logical and it is about the consequences of such actions that have nothing to do with the reporting product?! As we are still uncertain how to proceed in this particular case we prefer to play it safe and allow only "in-report" actions.
Kind regards,
Steve
the Telerik team
If we get back to this request and try to understand your particular scenarios, you most likely have a report that contains some kind of "commands" for your application that are not valid from outside the application, is that correct? Although we're not familiar with your application we would suggest extracting these actions from the reports to the application. This way the reports will contain only relevant information and will be really portable - that is you can export them to PDF or Excel and can open them outside your application.
That said the question that is bothering us is not technical but logical and it is about the consequences of such actions that have nothing to do with the reporting product?! As we are still uncertain how to proceed in this particular case we prefer to play it safe and allow only "in-report" actions.
Kind regards,
Steve
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0
Travis
Top achievements
Rank 1
Rank 1
answered on 25 Apr 2011, 03:23 PM
I think I've resolved this on my own. Part of my problem had to do with disabling an action based on individual row data. I was able to achieve this by using an expression in my "open drill down report" action. There are a few reasons why it would be nice to have custom action event handlers:
1. Greater flexibility
2. Greater portability - I say this because my application has two separate interfaces that use the same report. To somehow force these "actions" onto the application interface would mean I would have to duplicate the behavior in both interfaces.
1. Greater flexibility
2. Greater portability - I say this because my application has two separate interfaces that use the same report. To somehow force these "actions" onto the application interface would mean I would have to duplicate the behavior in both interfaces.