c2c-oerpscenario team mailing list archive

["Olivier Dony \(OpenERP\)" <777640@xxxxxxxxxxxxxxxxxx>]

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)

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/777640

Title:
  Journal_id, Period_id in account.move.line

Status in OpenERP Modules (addons):
  Confirmed

Bug description:
  Journal_id and Period_Id are repeatedly defined in Account.move and account.move.line which is not reasonable as long as I can not create different lines with different journals per move 
   _constraints = [
          (_check_centralisation,
              'You cannot create more than one move per period on centralized journal',
              ['journal_id']),
          (_check_period_journal,
              'You cannot create entries on different periods/journals in the same move',
              ['line_id']),
      ]

  Having said that, IMHO I do not see that need for redundancy in
  account.move.line as long as it is already defined in account.move.
  Furthermore, it is really and noticeably from past experience confuse
  the end user while doing data entry and decreasing the UX.