GitHub Issue 1219: Summary statistics fail with "Character read limit of 100000 exceeded" on wide datasets (Backport) - #7940
Merged
Conversation
… include view 'fields' info in post - backport from develop
labkey-susanh
approved these changes
Aug 17, 2026
cnathe
added a commit
to LabKey/testAutomation
that referenced
this pull request
Aug 17, 2026
… of 100000 exceeded" on wide datasets (Backport) (#3154) ## Rationale LabKey/internal-issues#1219 See related PR for rationale. This PR adds the test case. ## Related Pull Requests - #3081 - LabKey/platform#7940 - #3154 ## Changes - CustomizeViewTest test case for saveQueryView with wide column list in view
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rationale
Backport changes to 26.7 for https://github.com/LabKey/internal-issues/issues/1219
On wide grids (many columns), setting a summary statistic posts the full custom-view JSON to the saveQueryViews action, which is capped at
@JsonInputLimit(100_000)characters. The per-column field metadata array (fields) plus full column objects blow past that limit and the save fails ("Character read limit of 100000 exceeded"). The fix trims the POST body in_updateSessionCustomView: drop the unused top-level fields array and reduce each column to just fieldKey (+ title when present).Related Pull Requests
Changes