I am getting a strange error when users are selecting parameters on a report that result in several 1000 records being returned (which is what they want), and its for a limited set of users. This url https://docs.telerik.com/reporting/knowledge-base/json-length-is-too-large-net-core seems to indicate that less metadata will be returned when set. How/where can I see this metadata at runtime, either while running locally in visual studio or in the browser? I have tested it and it seems to work, but how can I verify this reduced volume of metadata?
searchMetadataOnDemand reportviewer setting - how to verify reduced metadata returned?
24 Views Asked by bitshift At
1
There are 1 best solutions below
Related Questions in TELERIK-REPORTING
- Binding ObjectDataSource Component to a DataSet
- C#/.NET - Working with Telerik.Reporting, how to get a Telerik.Reporting.Report from .trdp
- Telerik report designer using store procedure return multiple data sets how to access all data sets. report shows only top dataset result
- searchMetadataOnDemand reportviewer setting - how to verify reduced metadata returned?
- Telerik Report Designer Standalone - WPF - Invalid value of report parameter
- Blazor component - Failed to fetch dynamically imported module - telerikReportViewer
- Telerik Reporting Failed to connect to server
- How calculate a page header and footer running value in Telerik Reporting
- Issues with TelerikReports upgrade to 2023 R3, with Angular front end reports wrapper
- How to hide a sub report if no data - Telerik Report
- Value cannot be null. Parameter name: source in telerik
- Not able to open the Telerik report designer in VS 2022 and using .net 6.0
- Generating Telerik Report with Encrypted Custom Connection String without Using Web.Config Connection String
- Telerik Reporting ReportSerializable exception
- How to find available path bindings for a component in Teleriks Web Report Designer?
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
You may check the report HTML in the browser DevTools > Elements for the attribute 'data-search-id'. The meta information related to the Search functionality of the Telerik HTML5 Report Viewer consists of this additional attribute added to the searchable components.
If you render the report in a viewer with 'searchMetadataOnDemand' set to 'False' (default), the report is rendered with these additional attributes, and when the user clicks the 'Search' button, the viewer performs a single Search in a Document request that returns all data-search-id's that contain the searched text.
When 'searchMetadataOnDemand' is 'True', the report is rendered initially without the 'data-search-id' attributes. If the user clicks on 'Search', the report is generated once again completely to add all 'data-search-id' attributes, and then the viewer performs the 'Search in a Document' request.