Wrong type of argument in "create" and "write" of a osv_memory object

[Francois Degrave]

I create a osv_memory object in which there is a many2one relationship to an (osv) object.

I display this many2one as a selection field.

When the function "create" is called for this osv_memory object, the value of the many2one field is a string instead of an integer.

This can be problematic latter if "browse" is used (since it generates errors).

[Jignesh Rathod(OpenERP) (jir-openerp)]

Hello Francois Degrave,

I have tested your scenario at my end and it worked perfectly fine with many2one field.
Kindly check the video for reference.

Let me know with more information if still you face the same problem.

Thanks.

[Francois Degrave (fde-be)]

I'm sorry but I think you should first read in which branch I posted this bug. It is in WEB CLIENT. The video you recorded is in GTK client.

[Jignesh Rathod(OpenERP) (jir-openerp)]

Hello,

I have checked your scenario with latest updated code with web client and GTK client both but I did't face any problem.
Kindly check the video for reference.

Thanks.

[Francois Degrave (fde-be)]

Hi,

Yes indeed you are right. In fact I realized my problem is a bit more subtle than what I thought.

When I run a wizard from a view in which there is such a many2one with widget "selection", even if I didn't change anything, the client thinks the values changed because the value in the field many2one is a tuple, and what it reads from DB is a integer -- so they are different.

Therefore, if I cancel the wizard and try to re-run it just after, the client thinks there is a concurrency exception, since it tries to write but there wa

[Francois Degrave (fde-be)]

sorry I continue:

but there was another write since I first opened the view (the one ran when I first launched the wizard).

Thanks for your work,

François

[Vinay Rana (OpenERP) (vra-openerp)]

Thanks a lot for reporting this bug and contributing to OpenERP. Unfortunately the OpenERP Web Client project is not going to be developed further after the 6.0 series. As of 6.1 a newer and better web frontend known as the OpenERP Web project[1] will be available.
Our R&D developers normally work in Launchpad to fix bugs for the next release, but there will be no next release for the current OpenERP Web Client. As our resources are limited, all further R&D efforts from the Web team are dedicated to finish the new 6.1 OpenERP Web project[1].
This bug will be closed as "Won't Fix" to show that R&D won't be able to work on it.

Bugs affecting customers in production of course continue to be handled via the OpenERP Enterprise (OPW) maintenance service, and this is the recommended way to have them corrected directly in the 6.0 LTS stable branch.
You can find more details about all of this in the FAQ of our Bug Management Policy documentation[2].

If you are interested, you should soon be able to beta-test the new OpenERP Web 6.1 (this will be announced on OpenERP Community channels).

Thank you for your contributions and for your understanding!

[1] https://launchpad.net/openerp-web
[2] http://bit.ly/openerp-bugs-faq (FAQ #4)

[Francois Degrave (fde-be)]

Indeed that makes sense, I was wondering why there was still a "trunk" branch for the 6.0 web client...

I'm testing the new web client daily, and until now I must admit that some things are quite impressive, but also that most of the basic functionalities are either missing or buggy.

Anyway I'm convinced it is the way to go, however I hope it will be usable before release (in october, right?).