Odoo Help


No concurrency check when updating records

siddharth jambukiya
on 9/23/13, 11:40 AM 2,356 views

Only one user at any time should be able to edit a contract. We need to pop up a dialog box with details of the user that has the record open if another user tries to edit the record.

This obvious feature doesn't appear to be native to OpenERP.

Is there a module that implements this across the whole system?

Only one user at any time should be able to edit a contract. We need to pop up a dialog box with details of the user that has the record open if another user tries to edit the record. The 2nd user should then be prevented from editing the record until it is unlocked (i.e. the 1st user either saves or discards the record).

Seems odd that record locking is not part of the default Openerp architecture - do you know why?

Can we take a look at how we can implement this and come back with some ideas. It's not a burning priority at the moment but will be as soon as one/two of the users "discover" this issue.

Did you report a bug on Github ? Can you post the link ? Thanks.

Maxime Chambreuil
on 5/7/15, 11:16 AM

I reported the bug: https://github.com/odoo/odoo/issues/6737

Maxime Chambreuil
on 5/15/15, 4:52 PM

Andreas Maertens

--Andreas Maertens--
| 6 6 7
Finsterwalde, Germany
--Andreas Maertens--

I develop odoo8.0 modules

Andreas Maertens
On 3/6/14, 6:21 AM

The BaseModel in orm implements a function for that problem "_check_concurrency" that is called within the write method. For a reason I don't know the "_last_update" entry is never added to the context therefor that method is useless. Anyone does know more about?

On 6/4/18, 12:26 PM

Anyone tryied to make this feature work in Odoo 11? If yes, how did you managed to make it trigger the "_check_concurrency" in order to prompt an error if a user is updating a record that have been updated by another user?

We tryied in our team to follow the source code that lead us to the "__last_update" field, and we gave it a try by updating the context to add this field by overriding the method "read(self)" of the tested model, but it seems the verification on the file /odoo/odoo/models.py on the "def _check_concurrency(self)" always display a context without any "__last_update" fields, and we cannot wrap our head around this!!

Does someone also tryied to update the context? If yes, did you manage to trigger the checking by setting the context on the python side or javascript side or something else?

Martin Malorni
On 12/13/16, 12:34 PM

We have created a module that fixes the issues with the _check_concurrency function and we have improved on it as it was not covering some use cases. The module is available here. https://apps.openerp.com/apps/modules/9.0/concurrency/. The module can be made to work for v8 and v10 easily if there is an interest. It work in the enterprise version as well.


Ray Carnes

--Ray Carnes--
| 9 7 9
Keyport, United States
--Ray Carnes--

Senior ERP Analyst

OpenERP 6.1, 7.0; Odoo 8.0, 9.0, 10.0 and 11.0.

Completed Odoo Functional and Technical Training.

Functional Areas:

  • CRM/Sales

  • Inventory

  • Manufacturing

  • Accounting

  • Purchasing

Major Skills:

  • Business Process Reengineering

  • Efficiency Consulting

  • User Needs and GAP Analysis;

  • Functional and Technical Design;

  • Prototyping and Proof of Concepts;

  • Requirements Specifications;

  • Agile Implementation;

  • Data Migration;

  • Configuration & Customization (UI and code);

  • Integration - Odoo and non Odoo Applications and Services;

  • Training and Knowledge Transfer;

  • Go Live Support;

  • Helpdesk;

  • Version Upgrades and Migration.

  • Accounting Expert.

I have over 20 years of experience empowering and enabling users with enterprise information systems that make a real and measurable difference in their ability to proactively manage their businesses and organizations. 

I am a skilled Communicator and I only take the serious things seriously!

Ray Carnes
On 9/24/13, 2:52 AM

Conflicts when two people edit the same record are presented/resolved when they save.

Try it!

i am agree with you Ray carnes but conflicts occurs when two user try to edit same record and same field at a time...

siddharth jambukiya
on 9/24/13, 3:27 AM

I try and to me this is not working fine. I created an order. I click edit on that sale order with user admin. Then I used another user "laflammm" on another PC to edit the same order. Then I changed the Comment field to "whatever" with user "admin" then I saved. I returned on that same order opened by "laflammm" on another computer and changed the same field to "whatever2" and saved. I got no error to let me know I just overwrote the previous save done by admin!

Mathieu Laflamme
on 11/8/13, 3:33 PM

About This Community

This platform is for beginners and experts willing to share their Odoo knowledge. It's not a forum to discuss ideas, but a knowledge base of questions and their answers.


Odoo Training Center

Access to our E-learning platform and experience all Odoo Apps through learning videos, exercises and Quizz.

Test it now

Question tools

2 follower(s)


Asked: 9/23/13, 11:40 AM
Seen: 2356 times
Last updated: 6/4/18, 12:26 PM