Apr 3rd, 2011, 10:54 AM
Hey guys,
Hope all is well, Hannes. Man, you ask lots of difficult questions.
It's excellent.
So right now, no - this isn't possible. But you can do it with 2.1 - not so much with Views, but with fields themselves.
So in 2.1, any radio button group, checkboxes, dropdowns and multi-select dropdowns can get their options from either a Field Option Group or (what's new) from the contents of any other form field. This is a big improvement: it lets you link your data together between forms.
To take up your example, you would create 4 extra fields in your Order Form. These would be (say) dropdowns that are mapped to the name, street, city and email fields in the Registration form. Then, you'd add those fields to a View in your Order form (and make that View have those fields as editable). When you edited the Order form submission with that View, you could select the appropriate values from the dropdowns. They would be populated with all values from all submissions in the Registration form; e.g. the "emails" dropdown would contain everyone's email address. (Options appear with the submission ID in parentheses at the end, so you know for sure which registration you're dealing with).
Now here's the problem, which your post has made me understand better: this will be a pain to configure each time you create a new Order. You'd have to re-select the same person's info each time.
What we *really* need is a button on the Registration form's Edit Submission page saying "Create Order". This would create a new entry in the Order form table, link to it, and populate the values for the mapped fields. That way you could even make the View that you're linked to in the Order form have those fields non-editable, like you suggested.
I wonder if this should be a module? It seems a little specific to be in the core script. But I *do* see this as being extremely valuable: as soon as it becomes possible to map the fields between forms, your scenario will become more and more common.
Thoughts?
- Ben
Hope all is well, Hannes. Man, you ask lots of difficult questions.
It's excellent.So right now, no - this isn't possible. But you can do it with 2.1 - not so much with Views, but with fields themselves.
So in 2.1, any radio button group, checkboxes, dropdowns and multi-select dropdowns can get their options from either a Field Option Group or (what's new) from the contents of any other form field. This is a big improvement: it lets you link your data together between forms.
To take up your example, you would create 4 extra fields in your Order Form. These would be (say) dropdowns that are mapped to the name, street, city and email fields in the Registration form. Then, you'd add those fields to a View in your Order form (and make that View have those fields as editable). When you edited the Order form submission with that View, you could select the appropriate values from the dropdowns. They would be populated with all values from all submissions in the Registration form; e.g. the "emails" dropdown would contain everyone's email address. (Options appear with the submission ID in parentheses at the end, so you know for sure which registration you're dealing with).
Now here's the problem, which your post has made me understand better: this will be a pain to configure each time you create a new Order. You'd have to re-select the same person's info each time.
What we *really* need is a button on the Registration form's Edit Submission page saying "Create Order". This would create a new entry in the Order form table, link to it, and populate the values for the mapped fields. That way you could even make the View that you're linked to in the Order form have those fields non-editable, like you suggested.
I wonder if this should be a module? It seems a little specific to be in the core script. But I *do* see this as being extremely valuable: as soon as it becomes possible to map the fields between forms, your scenario will become more and more common.
Thoughts?
- Ben