← Back to team overview

c2c-oerpscenario team mailing list archive

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

 

Hello NOVOTRADE RENDSZERHÁZ,

Your patch as #4 (in which my changes are reverted) is not correct for
nested o2m case, Its create a problem to load new o2m form.

Please try and check the behaviour as under,

Sales > Configuration > Pricelists >  New (Products Price List)> New
(Pricelist Version) > New (Products Listprices Items).

There should be open New form of Products Listprices Items on First click only. 
But its save the parent record and do nothing for expected New Form open Because,
it does not find the value of terp_id, terp_model, terp_view_mode, etc..

So that changes are needed and Yes after that changes in revision 4566,
the problem faced with only view_mode which is solved in sma's branch as
#5.

So, both changes are needed for the nested o2m case and it works fine.

Thanks !

-- 
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/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



References