You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi here is an issue when a model plugged to base_tier_validation is displayed as a list in another form: when clicking a record in such a list, the view crashes:
Error: Missing field string information for the field 'need_validation' from the 'res.partner' model
You have to add need_validation field with invisiblity=1 in form view. To add field into view you need to inherit main form view and add field into inherited form view
You have to add need_validation field with invisiblity=1 in form view. To add field into view you need to inherit main form view and add field into inherited form view
Hi that indeed seems to be what's missing; the issue here is base_tier_validation users never added that so far (eg in sale_tier_validation).
Adding it by hand in each derived module seems cumbersome to me; especially when talking about modals such as that partner merge one which may well define their own views.
I think the assumption so far was that the mixin provided by base_tier_validation would inject these fields, same as it already injects some UI elements such as validation buttons.
Previous implementation was losing fields in some cases; new one
properly merges dicts/tuples.
This fixes odd "Missing field string information" errors in
form-embedded lists.
This cset also removes an obsolete `base_model_name` context key no
longer used in Odoo 16.
This cset adds a `test_get_view` test which checks for that
`need_validation` field; it was failing with the previous impl.
FixesOCA#825.
Hi here is an issue when a model plugged to
base_tier_validation
is displayed as a list in another form: when clicking a record in such a list, the view crashes:An easy way to test this is from a partner-contact runboat:
➔ Screenshot:
This isn't specific to that model nor to that wizard; I can also reproduce from a sale-workflow runboat in a more convoluted way:
sale_order_ids
field➔ Screenshot:
The text was updated successfully, but these errors were encountered: