gridcn2.0.0
Cheatsheets and messagesMessages

Add-on messages

Look up the warnings of the history, pinned rows, saved views, URL state, presence, comments, import and export, fill, and find and replace add-ons.

Most console warnings print only in a development build, and most print once. A word in angle brackets, such as <id>, stands for a value that the grid fills in. A message that ends in ... continues past the text that the table quotes. The tables leave out the backticks that some messages put around prop names.

Add-on warnings

Each other add-on prints its own prefix.

MessageWhat to doPage
[data-grid-history] onSkip threw:Fix the error in onSkip. The grid prints the error after the text. This one is a console error.Undo and redo
[data-grid-history] <undo|redo|record|rollback>() ran before the history plugin mounted, so it did nothing. Pass "plugin" (or "plugins" from useDataGridState) to the grid, and keep it in a plugins prop that you set after a spread.Pass the history plugin in plugins, and keep grid.plugins after a spread.Undo and redo
[data-grid-history] The history plugin never mounted, so undo and redo do nothing. Pass "plugin" (or "plugins" from useDataGridState) to the grid's plugins prop.Pass the history plugin in the plugins prop of the grid.Undo and redo
[data-grid-history] record() skipped an insert of a row that data already holds. record() writes the change itself, so the call is safe, but you do not need to apply it to your own array first.Call record alone and let onDataChange update your state.Undo for code changes
[data-grid-pinned-rows] onChange threwFix the error in the onChange of DataGridServerAggregateReporter. The grid prints the error after the text. This one is a console error.Show totals from a server
[data-grid-pinned-rows] useDataGridServerAggregate dropped the value of column "<id>": only text, finite numbers, booleans, and null are shown.Resolve only text, finite numbers, booleans, and null in fetchAggregates.Show totals from a server
[data-grid-views] two mounted grids with other columns share the views storage key "<key>", so each loads and overwrites the views of the other; pass each grid its own storage keyPass each grid its own storage key, for example useDataGridViews({ storage: "orders-views" }).Saved views
[data-grid-views] a callback threwFix the error in onValueChange or onError. The grid prints the error after the text. This one is a console error.Saved views options
[data-grid-comments] defaultComments threw, so the comments start empty: <error>Fix the function you pass as defaultComments. It runs once after mount and must return an array of comments.Comments options
[data-grid-comments] <n> seed record(s) were dropped (invalid or over a bound)Fix the records in defaultComments. Each record needs valid ids, finite times, and text within maxTextLength, and the set must stay within the bounds.Comments options
[data-grid-comments] <n> record(s) of the comments prop were dropped (invalid or over a bound)Fix the records in comments. Keep the set within the bounds.Comments options
[data-grid-comments] currentUser is present but invalid (id must be 1..128 characters without control characters); every comment write is refusedPass a currentUser with a valid id, or leave it out for anonymous comments. Use readOnly: !session while a session loads.Comments options
[data-grid-comments] <n> remote change(s) were dropped (invalid)Send valid CommentChange objects to applyRemote. The skipped list of the verdict names the dropped changes.Comments options
[data-grid-comments] <n> fetched record(s) were dropped (invalid)Resolve valid CellComment records from fetchComments.Comments options
[data-grid-comments] a stale rejection without current leaves Discard only; return current from the save, or set fetchCommentsReturn the current record of the server as current in a stale rejection, or set fetchComments so the add-on can load the row again.Comments options
[data-grid-comments] openComments dropped: the cell did not render within 10 framesCall openComments for a cell that the view can show.Comments options
[data-grid-comments] a callback threwFix the error in the callback that threw. The add-on prints the error after the text, and its other updates still run. This one is a console error.Comments options
[data-grid-url-state] dropped <n> URL layout entries for removed columnsYou need no fix. The URL named columns that do not exist.URL state
[data-grid-presence] setPresenceHighlights: kept the first <max> entries and dropped the restSend at most 1000 entries. Drop the peers that are off screen on your server.Presence options
[data-grid-presence] setPresenceHighlights: ignored a payload that is not an arraySend an array of entries. The call clears every highlight.Presence options
[data-grid-presence] setPresenceHighlights: dropped an entry — not an objectSend PresenceHighlightEntry objects.Presence options
[data-grid-presence] setPresenceHighlights: dropped an entry — missing or oversized idSend a non-empty string id of at most 256 characters.Presence options
[data-grid-presence] setPresenceHighlights: dropped an entry — rowId-native entries need a bounded rowId and columnIdSend a non-empty rowId and columnId of at most 256 characters.Presence options
[data-grid-presence] setPresenceHighlights: dropped an entry — rowId-native range entries need string arrays rowIds and columnIdsSend rowIds and columnIds as arrays of strings.Presence options
[data-grid-presence] setPresenceHighlights: dropped an entry — empty rowIds/columnIds paint nothingSend at least one row id and one column id.Presence options
[data-grid-presence] presence entry "<id>" has <n> columnId(s) not in the visible columns (hidden or unknown); those cells are droppedSend column ids of visible columns.Show presence
[data-grid-presence] presence entry "<id>" resolves to <n> fragments, above the <max>-rect budget; the excess is not painted (downsample the remote selection or filter it)Send a smaller selection for the remote user.Show presence
[data-grid-presence] onExcessRects threwFix the error in onExcessRects. The grid prints the error after the text. This one is a console error.Presence options
[data-grid-io] <format> export failedRead the error that the grid prints after the text.Export
[data-grid-fill] the fill target skipped <n> unloaded row(s) (lazy grid): unloaded cells are never filled and the selection still expands over them. Fill over a lazy grid covers loaded rows only.Load the rows before you fill over them.Fill handle
[data-grid-history] undo ran over a sparse (lazy) data array: unloaded rows are holes, so an undo that needs them is blocked and keeps its entry. Use a hole-tolerant getRowId and pass a datasetKey (or call clear()) when server.refresh() replaces the rows or the dataset changes.Pass a datasetKey, or call clear() when the rows change.Undo with server data
[data-grid-pinned-rows] useDataGridAggregate (scope "<scope>") skipped <n> unloaded row(s): the data array is sparse (lazy loading), so the result covers loaded rows only. Use server-side totals or compute them outside the grid.Compute totals on the server for a lazy grid.Pinned rows
[data-grid-pinned-rows] one serverAggregateRow is pinned more than once, so it fetches once per place. Create a second serverAggregateRow, or pin it once.Create a second serverAggregateRow, or pin it once.Pinned rows
[data-grid-pinned-rows] useDataGridAggregate: spec key "<columnId>" matches no column id and is ignored (check for a typo)Use a column id as the key of the spec.Pinned rows
[data-grid-url-state] two <hook> instances use <the prefix or no prefix>; give each grid its own prefixPass a different prefix to each DataGridUrlState, useDataGridUrlState, or useDataGridUrlPagination.URL state
[data-grid-url-state] dropped URL sort spec for removed, hidden, or unsortable column "<columnId>"You need no fix. The URL named a column that the grid cannot sort.URL state
[data-grid-url-state] dropped URL group for removed, hidden, or ungroupable column "<columnId>"You need no fix. The URL named a column that the grid cannot group.URL state
[data-grid-url-state] dropped URL filter spec for removed, hidden, or unfilterable column "<columnId>"You need no fix. The URL named a column that the grid cannot filter.URL state
[data-grid-io] export truncated to <maxRows> of <total> rows (maxRows)Raise the maxRows export option.Export options
[data-grid-io] buildImportedRows: grid column "<columnId>" is mapped by more than one import column - the first mapping winsMap each grid column from one import column.Import options
[data-grid-io] mapColumn rejected, so the built-in column match is usedFix the error in mapColumn. The grid prints the error after the text.Import options
[data-grid] the filter operator "<operator>" on column "<columnId>" has no match, so the grid does not narrow rows with it. Give it a match in the column's filter.operators, or use filterMode="server".Give the operator a match in the filter.operators of the column, or set filterMode to "server". The grid prints this once for each column and operator.Filtering
[data-grid-find-replace] processReplace returned no plan or more patches than replaceAllLimit; the replace is cancelledReturn a plan with at most replaceAllLimit patches from processReplace.Find and replace options
[data-grid-find-replace] processReplace threw; the replace is cancelledFix the error in processReplace. The grid prints the error after the text.Find and replace options
[data-grid-io] onBatch must return the byte size it kept as a finite number; this batch counts as 0 bytesReturn the byte size of the batch from onBatch as a finite number.Export the whole result
[data-grid-io] build() ran before a file was loaded and returns null; call loadFile() firstCall loadFile() and wait for the preview before build().Import options
[data-grid-io] formatCell returned a promise; use exportGrid or buildXlsx, which await itCall exportGrid, which awaits the promise. A synchronous CSV build takes a synchronous formatCell.Shape the export file
[data-grid-io] checkImport failedFix the error that the grid prints after the text, such as a failing request. The dialog shows labels.io.checkFailed and the import can be retried.Import options
[data-grid-io] print failedFix the error that the grid prints after the text, such as a failing source.Export
[data-grid-io] print css is longer than 65536 charactersShorten the css option of printGrid.Export
[data-grid-io] onProgress threwFix the error in onProgress. The grid prints the error after the text, and the export goes on.Export the whole result
[data-grid-io] export stopped at <n> rows (maxRows <max>, maxBytes <max>)Raise maxRows or maxBytes, or narrow the result on the server.Export the whole result
[data-grid-io] onImportError threwFix the error in onImportError. The grid prints the error after the text, and the dialog stays open.Import options
[data-grid-io] this grid holds a window of its result; pass onImport to send the rows to your serverPass onImport and send the rows to your server. The default append needs a grid without totalRowCount.Import into a server grid
[data-grid-io] build() found no grid; pass columns and cellTypes or call it under a DataGridProviderPass columns and cellTypes to useDataGridImportPreview, or call it under a DataGridProvider.Control the import
[data-grid-io] onImport rejected; the dialog stays openFix the error in onImport. The grid prints the error after the text.Import options
[data-grid-presence] setPresenceHighlights: dropped an entry — missing or malformed range (need finite x, y, width, height)Send finite numbers for x, y, width, and height.Presence options
[data-grid-presence] presence entry "<id>" references column "<columnId>" which is not in the visible columns (hidden or unknown); the entry is droppedSend entries for visible columns only.Show presence
[data-grid-presence] rows or columns moved while a view-space presence entry is active — its highlight position is now stale; use rowId-native presence entries for a live feedUse entries with a row id and a column id.Show presence

On this page