On 10 May 02:25, Simon Klemenc wrote: > > > On Sunday, May 10, 2015 at 12:44:13 AM UTC+2, Albert Cervera Areny wrote: > > > > 2015-05-09 22:47 GMT+02:00 Simon Klemenc <[email protected] > > <javascript:>>: > > > Hi, me once again... > > > > > > I need your advice as i'm running into concurrency exceptions from time > > to > > > time.... > > > Whenever that happens it results from a button triggered workflow > > transition > > > after changing some field without a save in between... > > > > > > How can i avoid these? > > > can the client be modified to trigger a save before certain actions? > > > > The client already saves before executing an action. > > > > Are you sure you did not modify that record from another tab after > > loading the record in the current one? > > > > > > > > best regards > > > > Hi albert, > Thanks for your message, > I investigated further and found that it is a result of record modification > in "validate"
I think it is semantically wrong to change a record during its validation. > So, is it better to move the logic to on_change or so? Hard to say without knowing what you try to achieve. > can a client update be triggered in validate? I don't understand what you mean. -- Cédric Krier - B2CK SPRL Email/Jabber: [email protected] Tel: +32 472 54 46 59 Website: http://www.b2ck.com/
