docs(viewer): state the row count rule for the unsearched view too

Follow-up to the previous commit on this branch, both wording fixes. - The sentence this branch deleted was the page's only description of the row count when no search is active - and that is the case where the count really can exceed the rows displayed (viewdata reports count(*) for the filtered view while the grid stops at DC_MAXOBS_WEBVIEW). State it, instead of leaving the page silent on the path readers use most. - "returns the first 500" claims an ordering the search does not apply: the search is a WHERE clause with no ORDER BY, so which 500 come back is whatever the engine hands over first. Say "returns 500 of them". Checked against viewdata.sas and mp_searchdata.sas on main: the search path passes outobs=DC_MAXOBS_WEBVIEW to mp_searchdata, which caps the result dataset in the same data step that builds it, and viewdata takes its row count from that dataset - so for a search the count and the rows are capped together.
2026-09-22 16:34:14 +00:00
parent 206d88c6a9
commit 99b2a7454e
1 changed files with 3 additions and 1 deletions
@@ -21,7 +21,9 @@ The search covers **every** column of the table at once, so you do not need to k
 - **Character search** (the default) is a case sensitive CONTAINS match against every character column, so `Smith` finds `Smithson` and `smith` finds `Goldsmith`, but `smith` will not find `Smithson`.
 - **Numeric search** (tick the Numeric box) is an exact match against every numeric column, so `42` will not find `420` or `4210`.
 - If a filter is applied, the search runs within the filtered rows rather than the whole table.
- The result set is capped by the [`DC_MAXOBS_WEBVIEW`](/dcc-options/#dc_maxobs_webview) option (500 rows by default). A search that matches more rows than the cap returns the first 500, and the row count shown next to the table name is that capped count, not the total number of matches.
+- The grid is capped by the [`DC_MAXOBS_WEBVIEW`](/dcc-options/#dc_maxobs_webview) option (500 rows by default).
 - For a search, the cap applies to the row count as well: a search that matches more rows than the cap returns 500 of them, and the count shown next to the table name is the number of rows returned, not the total number of matches.
 - Without a search, the count shown next to the table name is the full number of rows in the filtered view, so it can be higher than the number of rows displayed - a table of 1,200 rows reports `1,200 rows` above a grid holding the first 500.
 - A search that matches nothing shows a "No data found with given conditions" panel rather than an empty grid.
 ![Full table search](img/full-table-search.png)