Summary
In a multi-page app on a Cloud instance, a multi-select input writes its selections into a text column as a Postgres array literal (e.g. { value1, value2 }), but on subsequent pages the form's multi-select does not display those stored values even though the table shows the field.
AI Response
This is a data round-trip/formatting issue rather than a bug. The multi-select outputs a JS array, but once it is saved to a text column it comes back as a single string like {"value1","value2"}, and the component's Default value expects an actual array of strings — so it renders none or only one. Parse the stored string back into an array before binding it (e.g. {{ query.data.field.split("'").filter((_, i) => i % 2 == 1) }} for a Postgres array literal, or UNNEST the array in the read query), and make sure the saved values exactly match the option values, including type (string vs. number). Also note that the multi-select on each page is a separate component, so each page needs its own query that re-reads the record (e.g. via selectedRow or a URL param) and points the Default value at the parsed array.
Sources
Mult page app - Multi-select values are not being displayed on subsequent pages
A staff-diagnosed thread on the identical multi-page scenario, explaining that the saved string must be parsed back into an array for the Default value and that each page's multi-select needs its own query to re-read the record.
A solved thread with the exact { "value1", "value2" } storage format not displaying on load, where the fix is splitting the array-literal string into an array or using UNNEST in the query.
The Community Team is testing out a new automation. Let us know if it's helpful (or not) by leaving a 
, 
, or 
. Or by marking this post as the "Solution"! Let us know if you have any feedback here. 