[Solved] Issues with Search Feature in WPF Telerik Report Viewer

[John]

Hi,

We are currently implementing the Telerik Report Viewer in a WPF application using C#. However, clicking the search button triggers an error.

To resolve this, we attempted setting searchMetadataOnDemand = true, but it caused UI rendering issues across the entire application. We have attached our source code for your reference. Could you please guide us on the correct way to implement the search feature without disrupting the UI?

[Petar]

Hi John,

Thank you for sharing the code snippet of your viewer logic.

First, I would like to clarify that SearchMetadataOnDemand is not required to enable search functionality in the WPF Report Viewer. Search is enabled by default, even when this property is set to false. When SearchMetadataOnDemand is set to true, the viewer intentionally defers generating the report's search metadata until a search operation is initiated. While this can improve the initial loading time of larger reports, it also requires the report to be processed again when the user performs a search. If this behavior is not needed in your scenario, I would recommend removing this setting and allowing the viewer to use its default behavior.

With that said, I attempted to reproduce the issue locally by adding logic similar to the code you shared, but I was unable to observe the same behavior. For reference, I have attached the sample project that I used during testing. Could you please review it and let me know whether the issue is reproducible on your end?

Additionally, it would be very helpful if you could let me know which version of Telerik Reporting your application is currently using, as well as the exact exception that occurs when the Search button is clicked.

To help us investigate further, I would recommend enabling a trace listener in your application and sharing the generated log file, as it can be particularly helpful if the issue is caused by an exception being thrown internally by the viewer. For more information on how to enable trace listeners, please refer to the following articles:

• For .NET: Troubleshooting Reporting Implementation in ASP.NET Core Application
• For .NET Framework: How to: Create and Initialize Trace Listeners

Ideally, if possible, it would be very helpful if you could modify the attached sample project until the issue becomes reproducible and then send it back to us for investigation. However, if it is possible at the moment, the log file should suffice for now.

Thank you, and I am looking forward to your reply!

Regards,
Petar
Progress Telerik