openerp-india team mailing list archive

["Jignesh Rathod\(OpenERP\)" <1089902@xxxxxxxxxxxxxxxxxx>]

Hello,

I have checked your scenario as Cedric Le Brouster ,
I agree with << Cedric Le Brouster >> , When function field use store={} parameter it does not change
value next to the second.

For Example ...

Class

C -          Change field 
B -          Function field change value  on change of  C class field. [ Change Value ]
A-           Function field change value  on change of  B class field. [ Failed to called Function A ]

So class A function never called next to the second.

I am confirming this issue to improve function field for allow chain
update.

I have attached a test case [  function_field_chain.py ]

Thank you.



** Changed in: openobject-server
   Importance: Undecided => Low

** Changed in: openobject-server
       Status: New => Confirmed

** Changed in: openobject-server
     Assignee: (unassigned) => OpenERP's Framework R&D (openerp-dev-framework)

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Server.
https://bugs.launchpad.net/bugs/1089902

Title:
  fields function store attribute does not allow chain update

Status in OpenERP Server:
  Confirmed

Bug description:
  This problem occurs when a fields.function has another fields.function
  in its store={} parameter. The first function is never called next to
  the second one.

  For example :

  class A:
      'a_value' : fields.function(_update_value,
                                  store={'class_b' : _function,'b_value',10]},
                                  method=True, type='integer', string='value')

  class B:
      'b_value' : fields.function(_update_value,
                                  store={'class_c' : _function,'c_value',10]},
                                  method=True, type='integer', string='value')

  class C:
      'c_value' : fields.integer('value')

  Here, changing a c_value would change the b_value, but not the a_value.
  (With b_value set as readonly='false', we could change it manually and see that the a_value is correctly recalculated.)

  Tested with nightly build : openerp-6.1-20121213-004437

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-server/+bug/1089902/+subscriptions