Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000405Openbravo ERP00. Application dictionarypublic2008-05-22 15:322008-07-01 17:56
Reporteralostale 
Assigned Toalostale 
PriorityhighSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target Version2.40Fixed in Version2.40alpha-r3 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0000405: Database error creating new Settlement
DescriptionThe first created settlement seems to be ok, but after saving the interface looks like new record (pencil with star, save button available...) if save button is pressed again "database error" message is raised.
Steps To Reproduce1. Log out
2. Log in
3. Set Openbravo admin role
4. Go to Financial Management || Receivables & Payables || Transactions || Settlement
5. Click new
5.1 Look the proposed document no is not at the range it should be
6. Save
6.1 Note that although the success message appears the interface looks like new record
7. Save
7.1 Database error message
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
depends on defect 0000411 closed alostale Database error creating new Settlement 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2008-05-22 15:32alostaleNew Issue
2008-05-22 15:32alostaleAssigned To => cromero
2008-05-22 15:32alostaleOBNetwork customer => N
2008-05-22 15:37alostaleNote Added: 0000305
2008-05-22 15:37alostaleStatusnew => scheduled
2008-05-22 15:37alostaleAssigned Tocromero => alostale
2008-05-22 15:38alostaleStatusscheduled => resolved
2008-05-22 15:38alostaleFixed in Version => trunk
2008-05-22 15:38alostaleResolutionopen => fixed
2008-05-22 15:38alostaleNote Added: 0000306
2008-05-22 17:44alostaleStatusresolved => new
2008-05-22 17:44alostaleResolutionfixed => open
2008-05-22 17:44alostaleStatusnew => scheduled
2008-05-22 17:44alostaleStatusscheduled => resolved
2008-05-22 17:44alostaleResolutionopen => fixed
2008-06-11 14:47cromeroTarget Version => 2.40
2008-06-11 14:50cromeroFixed in Versiontrunk => 2.40alpha r3
2008-06-19 11:29plujanStatusresolved => closed
2008-07-01 17:56anonymoussf_bug_id0 => 2007884

Notes
(0000305)
alostale   
2008-05-22 15:37   
The cause of this issue is that auxiliar input variables are read and set as session variables after the initialization for new field.

So this is happening when the session has not yet the session values set for all the windows that use auxiliar inputs and are accessed by default in relation mode.
(0000306)
alostale   
2008-05-22 15:38   
r4465.