← Back to team overview

c2c-oerpscenario team mailing list archive

[Bug 699748] Re: [6.0 RC2] - strange and different behaviour of GTK and WEB client

 

I think it is not the same case as 698021.

In the account.move.line.write() case, we are doing something extreme:
we have a write() definition with more arguments than a standard
orm.orm.write() function. This might be part of the problem, since some
other object might be calling move_line.write() without clearing the
'update_check' flag.

In some sense, this bug may uncover a deeper problem of our framework:
sometimes we need to pass extra information through the "context" dictionary, but don't wish to expose that option to the remote (RPC) client.

/me thinks of a solution... To be continued..

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

Title:
  [6.0 RC2] - strange and different behaviour of GTK and WEB client

Status in OpenObject Web Client:
  Triaged
Status in OpenObject Server:
  Triaged

Bug description:
  the attached module allows (or should do so  ) to change account_id of posted account move line (Journal Items)

Web - calls the account_move_line.write() twice
* once with the correct parameter update_check = False
* and a second time with update_check = True

GTK - seems not to do this, but does not refresh the display not showing the new account - this is shown correctly only after manual refresh 

 I'd expect the same behaviour for both clients.

If it's not a misconception of my module it might cause very wired behaviour





References