Notes |
|
(0055973)
|
jonalegriaesarte
|
2013-01-30 13:59
|
|
Moved to MP21 because it needs to be tested in depth. In any case, the patch is attached to test it. |
|
|
(0056033)
|
mtaal
|
2013-02-01 08:08
|
|
Hi Augusto,
The diff looks fine, but one question. I see this
record['_hasValidationErrors'] = true
but I don't see any code to set it back to false or to remove the hasValidationErrors.
I will close/check the issue again for MP21, okay?
gr. Martin |
|
|
|
Thanks Martin.
I saw no need to delete/reset the _hasValidationErrors property because when the record is saved without validation errors that property is no longer present in that record. |
|
|
(0056039)
|
mtaal
|
2013-02-01 09:45
|
|
Ok, my impression is that the record will stay in memory during the lifetime of the grid/form. But I am not sure...
gr. Martin |
|
|
(0056394)
|
hgbot
|
2013-02-12 13:33
|
|
Repository: erp/devel/pi
Changeset: 66e71edf502a8804809950b477858294ca8bf7d6
Author: Augusto Mauch <augusto.mauch <at> openbravo.com>
Date: Tue Feb 12 13:29:13 2013 +0100
URL: http://code.openbravo.com/erp/devel/pi/rev/66e71edf502a8804809950b477858294ca8bf7d6 [^]
Fixes issue 22766: Information is not lost when saving a record with errors
The problem was that when a record was saved and in the saving process it was returned with validation errors, the record was being cleared from the grid. This happened because the List
Grid recordHasChanges function returned false (the record had changes indeed, in fact it was not yet saved in the database).
This has been fixed by overwritting the recordHasChanges function, so that it always returns true if the record had validation errors. In that case we can be sure that the record has ch
anges, because we know that a record with validation changes can not be saved in the database.
---
M modules/org.openbravo.client.application/web/org.openbravo.client.application/js/grid/ob-view-grid.js
---
|
|
|
|
|
|
(0056955)
|
mtaal
|
2013-03-04 09:36
|
|
|