Feature request #10246
One to many relation: add child table also to custom forms
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: | - | ||
| Category: | Attribute table | ||
| Pull Request or Patch supplied: | No | Resolution: | fixed/implemented |
| Easy fix?: | No | Copied to github as #: | 18683 |
Description
Currently, the child table is displayed only when using autogenerated forms. It would be very good to have the same also for custom (drag&drop) forms.
History
#1
Updated by Matthias Kuhn about 10 years ago
- Resolution set to fixed/implemented
- Status changed from Open to Closed
That is already possible. Just drag the relation into the designer tree.
#2
Updated by Paolo Cavallini about 10 years ago
Brilliant, thanks - sorry for the noise.
Is this added to the manual?
#3
Updated by Matthias Kuhn about 10 years ago
Not sure about this...
But I assume it will have a better visibility once the redesign of the fields tab is done. Would be good if somebody takes the lead on this.
#4
Updated by Paolo Cavallini about 10 years ago
You mean the lead on development or documentation?
#5
Updated by Matthias Kuhn about 10 years ago
I meant the redesign.
But it counts for the documentation as well. Although I think we should wait with the documentation for the redesign, so we don't encourage people to learn a workflow that is going to change soon.