grid.import.apply changes the grid's own rows, which only a memory-source grid holds. On a remote, paged or stream source the rows come from the backend; import the file there, or load a memory grid from grid.import.csv(text).

Warnings reference › import.apply.source

Identifier

import.apply.source

Raised by

The grid (core)

Since

1.38.0

What happened

import.apply writes the imported records into the grid's own row set, and only a memory source has one. On any other source the rows come from the backend, so the import is refused and null returned rather than producing rows that the next fetch would wipe out.

The fix

Import the file on the server, or build a memory-source grid from the parsed records.

Reference

Covered in full at the API reference.