DataProcessor doesn't call onAfterUpdate when status >= 400

Suite and Optimus Suite 5
#1

Hi,
since version 4.1 it introduced a regression in our test when we return conflict HTML status code 409 (cause we track version and avoid updating same entry simultaneously). In the past, we were able to handle it in our onAfterUpdate call, but it seems that this is not called anymore when we return a status code >= 400 and it now issue a LoadXMLError which is not really the case ? The current XML that we return is valid, why would it think that the XML is not valid and not let the onAfterUpdate handle this ? It feels that if we return type=error, we should still get onAfterUpdate no matter the status code.

Thanks
Sylvain

#2

In your case data saving operations returns error status code, so onAfterUpdate event of dataprocessor will not be triggered.

In your case this code has a special meaning, but in other cases it can mean just some conflict on server side.

Same reaction will be on any status code >= 400

The only way to change behavior is through code modification ( you can locate and change the .status<400 in the code of dhtmlx.js )