Some questions (search feature, report viewer, WPF binding support)

[ClausDC]

I'm evaluating Telerik Reporting at the moment to see if it fits our needs for our WPF based application and would like to ask a few questions:

- In your "Known Limitations" stickied post you mention that a "search" feature is not implemented yet. Does that mean there is no support for text search (think ctrl+f like search) in the report viewer so that users can search for specific text strings? If true, can you give me an idea when you are planning to implement this feature? This feature is very important for us because we have some large reports where users sometimes look for specific text items and would be lost without a proper search function.

- Is it possible to hide the toolbar in the WPF viewer and implement our own controls for "next page", "print" etc.? Does the WPF report viewer support WPF command bindings for these functions?

- Going a step further from the previous question: In what extend does Telerik Reporting support the WPF binding engine? I mentioned command bindings for the viewer but can you give me some more details on this topic and/or future plans?

Many thanks!

[Peter]

Hi ClausDC,

Currently we don't have out of the box search functionality that is invoked with ctrl+f. Generally search functionality is in our TODO list and once we start working on it, we will add it to the Roadmap. In the meantime to improve the navigation within the reports our suggestion is to use a Document Map if applicable for your scenario. Additionally you can export the report to a format such as PDF, Excel or Word where searching is accomplished by the viewing software.

The WPF Report Viewer is actually a template, thus you can easily modify it with Blend. However you will have to override the command bindings.

There is nothing special in the WPF Report Viewer regarding the binding engine.

Best wishes,
Peter
the Telerik team

[Owen]

I have had to add a search function to our web site that is using your reporting controls. It would have been much easier if conditional formating let you test what rendering engine was building the report so that HTML pages could have addition functionality that is not used in PDF or other "printed" format reports.

Anyone wishing to discuss how I did this can contact me at [e-mail]