weird [DM_SYSOBJECT_E_VERSION_MISMATCH] error

the related error occurs when a object is saved. DFC checks the i_vstamp attribute of the object you previously obtained with dfSession.getObject() and the current i_vstamp value of the object in the repository. If the values are different, it means that the object was in the meantime changed -> DFC throws that error.

 

Calling fetch() , the object is reloaded from the docbase and it is in the actual state(i_vstamp is now the same as in the docbase) and the save method can process without any problem.

 

be aware tho, that calling fetch() has a big overhead.  Try finding why it is happening rather than just calling fetch() .