assembleValuesTocreate, assembleValuesToStore and assembleKeysToRemove are called multiple times during a synchronization (depending on the syncSplitMillis and the time period to synchronized). There is in theses methods a check to see if at the next call, the method needs to look for values. This check depends only on entity without values at the current run, which is not enough Solving issue described and fixing the assembleKeysToRemove that was using nextUpdateTxTime instead of nextRemoveTxTime jleroux: functional changes from patch, only formatting git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@1222105 13f79535-47bb-0310-9956-ffa450edef68