Hi, I’ve read these posts dealing with WIX DB atomicity/ transaction/ record locking. https://www.wix.com/velo/forum/coding-with-velo/atomicity-when-updating-a-field-in-collection https://www.wix.com/velo/forum/coding-with-velo/avoid-duplicates-in-database-in-case-of-concurrent-data-inserts https…

There are 2 solutions, but I will give you the most reliable one. You put a unique index on invoice number, write it, catch a possible DUPS error, if so, raise number by increment (like 1), write to db again, until no more DUPS error.

Collection (not record) locking

Ask the community

Netanel_Elbaz January 7, 2024, 9:20pm 3

What is the solution for the invoice number duplication you mentioned?

Topic		Replies	Views
[Solved] Question about record locking and one user overriding another’s data Ask the community code , question	7	452	May 30, 2020
Avoid duplicates in database in case of concurrent data inserts. Ask the community code , question	3	488	June 18, 2023
User Database Ask the community code , question	16	1205	December 30, 2017
Create an unique _id for each form submission Ask the community code , question	17	6885	May 30, 2019
wixdata create duplicate entry when insert Ask the community code , question	5	806	September 30, 2019

Collection (not record) locking

Related topics