Comment 5 for bug 777640

On 13. 05. 11 16:43, Olivier Dony (OpenERP) wrote:
> After discussing in R&D, here is a bit or rationale for these fields:
> - they are needed for performance reason on account.move.line to avoid indirect lookups every time
> - they must be exposed sometimes to the user, e.g. when doing manual journal entries (no parent move exists to take the values from)
>
> However, as described in this bug and its duplicate(s), the current
> implementation indeed needs to be improved with regard to values
> copy/sync and field visibility, in the following manner:
>
> 1) Values copy/sync: if possible the fields should be converted to
> fields.related, so that their values are properly synchronized/shared
> between lines and their move. If fields.related does not work because of
> the journal items line-by-line creation, then perhaps this can work with
> function fields instead.
>
> 2) Visibility: the default form and tree views for account.move.line
> should never contain these fields. They should only appear when the
> stock move values are not directly visible (probably mainly in the
> Journal Items menu)
>
> I am confirming the current bug (which has a better description) and
> marking bug 713539 as a duplicate.
>
> ** Changed in: openobject-addons
> Importance: Undecided => Low
>
> ** Changed in: openobject-addons
> Status: New => Confirmed
>
> ** Changed in: openobject-addons
> Milestone: None => 6.1
>
> ** Changed in: openobject-addons
> Assignee: (unassigned) => OpenERP R&D Addons Team 3 (openerp-dev-addons3)
>
Good that is moving forward! This is a rather "old" story...

thank you!
bogdan