Thank you for reporting this bug. We will make it our priority to review this report.
[5.1] Unused field replied by server causes model to be dirty after save
[5.1] Unused field replied by server causes model to be dirty after save
There are some properties the server of our application replies that are ignored by our client app as they aren't of any use.
Up to version 5.0, this wasn't a problem. However now in version 5.1 this is an issue, because these properties are checked by model after an update, even if unused, and may cause model to be dirty when he really shouldn't be.
Below it is an example reproducing the problem, you just need to edit the grid with a new value that fake server will reply a response with a different value for unused field and this will cause record to be dirty even after saved with all relevant client fields:
[5.1] Unused field replied by server causes model to be dirty after save
Aucun commentaire:
Enregistrer un commentaire