openerp-dev-web team mailing list archive

["Jiten \(OpenERP\)" <733089@xxxxxxxxxxxxxxxxxx>]

Thanks for reporting this, I have tested as your description for nested
o2m and faced the same problem.

I have tested with,
Sales > Configuration > Pricelists >New (Create new record) > New (Pricelist Version) > New (Products Listprices Items)
- Now first click on button "New" it saves the parent record but could not open next form And it opens after second click.

So, I have fixed this problem with revision number 4635 in dev branch like,
lp:~openerp-dev/openobject-client-web/trunk-bug-733089-jra .

Revision info:
4635 jra@xxxxxxxxxxx-20110331102220-zo1ob42sf7mj8o2y


** Changed in: openobject-client-web
       Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of OpenERP
SA's Web Client R&D, which is a bug assignee.
https://bugs.launchpad.net/bugs/733089

Title:
  when nested o2m are there. `New` for o2m does not work when o2m-
  level>1 in first go (when parent is not saved yet)

Status in OpenERP Web Client:
  Fix Committed

Bug description:
  Hello,

  When we have nested o2m in an object, and assuming we are not saving parent record manually and no o2m is inline-editable.
  on click of `New` for first-level o2m (say X) works fine, and opens empty-X-form in frame dialog
  now in X's form, for second-level o2m (say Y) when we click on `New`, it saves X(means its parent) but could not open Y's form in first click. but once X is saved (manually or indirectly), we can create Y successfully.

  Some fields of DOM could not be find in `edit` function of `One2Many` javascript class in first go when o2m-level>1.
  you can test this in Human Resources -> Configuration -> Payroll -> Salary Structure (to test no o2m should be inline editable)

  Note: this bug exist in web-client-trunk