Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0026262Openbravo ERPA. Platformpublic2014-04-12 03:272014-10-01 16:26
pjuvara 
AugustoMauch 
immediatecriticalhave not tried
closedfixed 
5
pi 
3.0PR14Q23.0PR14Q2 
alostale
No
Core
Pre packaging ( pi )
2014-02-28
main
https://code.openbravo.com/erp/devel/pi/rev/22299 [^]
No
0026262: Cannot update records
Whenever you try to update records, you get an error message:

Error
Saving failed. The record you are saving has already been changed by another user or process. Cancel your changes and refresh the data by clicking the refresh button.

See attached screenshot
Query a record and try to save a change.
No tags attached.
png Openbravo Payment Term N A.png (110,857) 2014-04-12 03:27
https://issues.openbravo.com/file_download.php?file_id=6829&type=bug
png
Issue History
2014-04-12 03:27pjuvaraNew Issue
2014-04-12 03:27pjuvaraAssigned To => AugustoMauch
2014-04-12 03:27pjuvaraFile Added: Openbravo Payment Term N A.png
2014-04-12 03:27pjuvaraModules => Core
2014-04-12 03:27pjuvaraTriggers an Emergency Pack => No
2014-04-14 13:33alostaleOBNetwork customer => No
2014-04-14 13:33alostaleRegression level => Pre packaging ( pi )
2014-04-14 13:33alostaleRegression introduced by commit => https://code.openbravo.com/erp/devel/pi/rev/22299 [^]
2014-04-14 13:33alostaleNote Added: 0066379
2014-04-14 13:33alostalePrioritynormal => immediate
2014-04-14 13:33alostaleTarget Version => PR14Q2
2014-04-14 13:39alostaleRegression date => 2014-02-28
2014-04-14 14:13AugustoMauchIssue Monitored: alostale
2014-04-14 14:13AugustoMauchReview Assigned To => alostale
2014-04-14 14:14hgbotCheckin
2014-04-14 14:14hgbotNote Added: 0066380
2014-04-14 14:14hgbotStatusnew => resolved
2014-04-14 14:14hgbotResolutionopen => fixed
2014-04-14 14:14hgbotFixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/f61bf8d6176d405b82a328cd9231e96c171505de [^]
2014-04-14 19:25plujanIssue Monitored: plujan
2014-04-15 07:50alostaleNote Added: 0066405
2014-04-15 07:50alostaleStatusresolved => closed
2014-04-15 07:50alostaleFixed in Version => PR14Q3
2014-04-15 08:12alostaleStatusclosed => new
2014-04-15 08:12alostaleResolutionfixed => open
2014-04-15 08:12alostaleFixed in VersionPR14Q3 =>
2014-04-15 08:12alostaleStatusnew => scheduled
2014-04-15 08:12alostalefix_in_branch => pi
2014-04-15 08:13alostaleStatusscheduled => resolved
2014-04-15 08:13alostaleFixed in Version => PR14Q2
2014-04-15 08:13alostaleResolutionopen => fixed
2014-04-15 08:13alostaleStatusresolved => closed
2014-05-07 18:11hudsonbotCheckin
2014-05-07 18:11hudsonbotNote Added: 0066927
2014-10-01 16:26plujanRegression introduced in release => main
2014-10-01 16:26plujanfix_in_branchpi =>

Notes
(0066379)
alostale   
2014-04-14 13:33   
Regression introduced by Absolute Time Project
(0066380)
hgbot   
2014-04-14 14:14   
Repository: erp/devel/pi
Changeset: f61bf8d6176d405b82a328cd9231e96c171505de
Author: Augusto Mauch <augusto.mauch <at> openbravo.com>
Date: Mon Apr 14 14:12:57 2014 +0200
URL: http://code.openbravo.com/erp/devel/pi/rev/f61bf8d6176d405b82a328cd9231e96c171505de [^]

Fixes issue 26262: Dates with negative offsets are formatted properly

The proper javascript format for dates and datetimes with timezone offset if the following: 2009-12-06T15:59:34+01:00. There if a method in charge of adding the semicolon in the datetime part in case it is missing.

Due to a bug in that method, the semicolon was not being added in dates with negative timezone offset. This resulted in a failure in the parsing of that date in the client side, being the date object actually modified when it was parsed.

In Openbravo there is a safety mechanism that detects if a record has changed based on its updated field. The updated field was being improperly modified in the client, so the safety mechanism was assuming that the record had actually been changed by another user, and was preventing the record from being saved.

---
M modules/org.openbravo.service.json/src/org/openbravo/service/json/JsonUtils.java
---
(0066405)
alostale   
2014-04-15 07:50   
Tested with:
-server in different time zones (negative and positive offset)
-client and server in different time zones
(0066927)
hudsonbot   
2014-05-07 18:11   
A changeset related to this issue has been promoted main and to the
Central Repository, after passing a series of tests.

Promotion changeset: https://code.openbravo.com/erp/devel/main/rev/02ca2648bcdc [^]
Maturity status: Test