Currently we can read a parent field in an inner form but we would need the reverse: being able to set a parent field from inner form in on_change method
Currently we can read a parent field in an inner form but we would need the reverse: being able to set a parent field from inner form in on_change method.
We would use a syntax like:
return {'value'
see details here: http://
A typical use case where this would dramatically improve the user user experience is the product configurator module:
"product_
But because we can't update the parent form, when dealing with variant dimension values, we can't do that and user has to click back in the parent form and look up for a matching variant manually, still there is only one, it will auto-complete. Still that's a good 4 clicks more and awkward workflow...
NB: that would required support from the clients
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by