Hi Jiten, Yes you are right!
If I apply this two patch it resolve the problem. http://bazaar.launchpad.net/~openerp/openobject-client-web/6.0/revision/4566 http://bazaar.launchpad.net/~openerp-dev/openobject-client-web/6.0-opw-5073-sma/revision/4575 If you add my two patch you get the same code ** Patch added: "novotrade_patch_web_60_733089_second.patch" https://bugs.launchpad.net/openobject-client-web/+bug/733089/+attachment/2063348/+files/novotrade_patch_web_60_733089_second.patch -- 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 Released Status in OpenERP Web Client 6.0 series: Fix Committed Status in OpenERP Web Client trunk series: Fix Released 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 _______________________________________________ Mailing list: https://launchpad.net/~openerp-dev-web Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-dev-web More help : https://help.launchpad.net/ListHelp
