openerp-dev-web team mailing list archive

Thread
Date

[Bug 733089] [NEW] when nested o2m are there. `New` for o2m does not work when o2m-level>1 in first go (when parent is not saved yet)

To: openerp-dev-web@xxxxxxxxxxxxxxxxxxx
From: Launchpad Bug Tracker <733089@xxxxxxxxxxxxxxxxxx>
Date: Fri, 11 Mar 2011 10:17:31 -0000
Reply-to: Bug 733089 <733089@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Devishree Brahmbhatt (OpenERP) (dbr-openerp) has assigned this bug to you for OpenERP Web Client:

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

** Affects: openobject-client-web
     Importance: Low
     Assignee: OpenERP SA's Web Client R&D (openerp-dev-web)
         Status: Confirmed

-- 
when nested o2m are there. `New` for o2m does not work when o2m-level>1 in first go (when parent is not saved yet)
https://bugs.launchpad.net/bugs/733089
You received this bug notification because you are a member of OpenERP SA's Web Client R&D, which is a bug assignee.