Repeating Sub-Form / Table Option
Permalink Browser Info Environment
I want to enter customer information once, then have the items they are custom ordering listed. If they are only ordering one item it is easy enough, but if they are ordering more than one item, from more than one vendor, etc, then I need to be able to track those separately, because it is likely that the items will not be received at the same time.
How difficult would it be to have the option for a "form within a form" and for the data entry format to be a table?
For example:
ItemNumber | Vendor | Qty | Description | Ordered? | Received? | Notified? | Expired? | Completed
It would be great to have multiple nesting options too. So, for example the Notified? column could contain multiple contact dates and whether contact was made or a message was left.
It would seem to me that this could be built out to be flexible enough to make both scenarios possible.
How difficult would it be to have the option for a "form within a form" and for the data entry format to be a table?
For example:
ItemNumber | Vendor | Qty | Description | Ordered? | Received? | Notified? | Expired? | Completed
It would be great to have multiple nesting options too. So, for example the Notified? column could contain multiple contact dates and whether contact was made or a message was left.
It would seem to me that this could be built out to be flexible enough to make both scenarios possible.
Type: | Discussion |
---|---|
Status: | New |
I've considered situations like this, but there is such a range as to the functionality that people might need that it's hard to make a one-size-fits-all solution. It could be done with some customization, but I don't think this is something that could be built into the core.
What if there was a Nested field type that allowed you to essentially add a form within a form, and included options for different ways to interact with the sub-form?
Allow front end add of additional rows? Yes/No?
Sum one or more "columns"? Yes/No?
(If Yes, then allow columns to be selected)
CSS options
I would first design the table form using all of the field types already available, and then create the overall form with the nesting characteristics/field type.
If it was well thought out, you could nest multiple layers creating a flexible framework that would allow the form designer the ability to create a custom solution from a one-size-fits-all structure.
Maybe I'm just being too much of an idealist! ;)
Allow front end add of additional rows? Yes/No?
Sum one or more "columns"? Yes/No?
(If Yes, then allow columns to be selected)
CSS options
I would first design the table form using all of the field types already available, and then create the overall form with the nesting characteristics/field type.
If it was well thought out, you could nest multiple layers creating a flexible framework that would allow the form designer the ability to create a custom solution from a one-size-fits-all structure.
Maybe I'm just being too much of an idealist! ;)