We convert all the fields that were storing python code into PYSON.
We add a pyson attribute on field tag to store PYSON value.
issue4416
review6971002
Currently, the "Open Reconcile Lines" can become very difficult to use when you
have a lot of different parties and/or a lot of account to reconcile.
Here is a new process which is based on a wizard that loops over all the couple
of account/party that potentially have lines to reconcile. It shows for each
couple a proposal of reconciliation that the user can accept or modify (with
write-off possibilities).
The proposal is found by testing all the combinations of lines up to 10 lines by
default (configurable). As such problem is NP-hard, I think we can afford to use
the brute force for small number and let the user solves higher number or
iterate on running the wizard. Any way, it is possible to implement other
strategy by module extention.
issue4185
review14511002
Only active_mode, active_id and active_ids can be used on relate domain because
it is the only values which could be sur to be present.
Also it always try to use active_ids over active_id to give more possibilities
to the user.
issue2474
review3261002
Since client hide the reverse one2many, it is no more possible to see the lines
that compose a reconciliation. This relate allow to show them back.
review1771003
Default value of company should be -1 to get the right cast and an impossible
value.
Replace False by None as other value in "in" clause.
issue3394
review1119002
* Rename:
- Move.name into number
- Move.reference into post_number
- MoveLine.reference into description
* Remove name and active on move line
* Add origin field on Move
issue2056
review503006
Cédric Krier