Hi everyone, I just started using NocoBase, and while trying things out, I came across a question. I’m not sure if this is the right place to ask, but I’ll give it a try.
My question is: when the collection is the same, the table–detail view works together just fine, but why doesn’t it work the same way with table–form(of data from selected row)?
From what I’ve tried, the form only seems to link with a row when it’s used in a popup. What do you think?
Yes, that’s correct.
A standalone form block is treated as a new record form, so it isn’t automatically linked to existing data.
If you want the form to load and edit the selected row’s data, you need to place it inside a popup that’s opened from the table (for example, using an “Edit” action).
In that case, the form will receive the selected record and work as an edit form.
Got it, thanks!
I don’t fully understand the design behind it yet, but I get that a standalone form is meant to create new records, not edit existing ones — that’s intentional, right?
That clears things up a lot — appreciate your explanation!
(The note below was added later.)
And one more thing — it might be convenient to have a container block that works the same way as the popup form, but stays statically on the page.
Yes, the 2.0 alpha version already supports standalone form editing blocks. You can schedule a demo to try it out, or experience it directly in our test demo. Please note that version 2.0 has not been officially released yet and is still in the testing phase.
