I’d recommend using a plain defsc for a single item, or a read-only form.

My reasoning was that a read-only form is a view of a single item, and you need an ID a the list of things you want to see, and you want to lay them out.

you can create custom resolvers to create virtual attributes, which can be displayed in such a form

You suggest leaning towards a RO form over a plain defsc? I guess using a RAD form just helps stick to the RAD approach over dropping down to Fulcro?

> As you can see there is some overlap in forms and reports. A read-only form is very much like a report, and a report with sufficient "row actions" (i.e. each cell can be clicked to edit) can behave very much like a form. Makes sense then. I've been avoiding RAD forms because I'm not intending to collect any input, but I know there have been many form improvements made recently, so why not. Thanks @tony.kay.

The only downside of using a RO form is that I have not, myself, needed to do that, so some of the SUI plugin controls might have bugs or not look great. PRs welcome.

Hi @tony.kay. It works! Thank you very much for your effort.