Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0000405
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] 00. Application dictionarymajoralways2008-05-22 15:322008-07-01 17:56
ReporteralostaleView Statuspublic 
Assigned Toalostale 
PriorityhighResolutionfixedFixed in Version2.40alpha-r3
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version2.40
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
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
Summary

0000405: 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
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
depends on defect 0000411 closedalostale Database error creating new Settlement 

-  Notes
(0000305)
alostale (viewer)
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 (viewer)
2008-05-22 15:38

r4465.

- Issue History
Date Modified Username Field Change
2008-05-22 15:32 alostale New Issue
2008-05-22 15:32 alostale Assigned To => cromero
2008-05-22 15:32 alostale OBNetwork customer => N
2008-05-22 15:37 alostale Note Added: 0000305
2008-05-22 15:37 alostale Status new => scheduled
2008-05-22 15:37 alostale Assigned To cromero => alostale
2008-05-22 15:38 alostale Status scheduled => resolved
2008-05-22 15:38 alostale Fixed in Version => trunk
2008-05-22 15:38 alostale Resolution open => fixed
2008-05-22 15:38 alostale Note Added: 0000306
2008-05-22 17:44 alostale Status resolved => new
2008-05-22 17:44 alostale Resolution fixed => open
2008-05-22 17:44 alostale Status new => scheduled
2008-05-22 17:44 alostale Status scheduled => resolved
2008-05-22 17:44 alostale Resolution open => fixed
2008-06-11 14:47 cromero Target Version => 2.40
2008-06-11 14:50 cromero Fixed in Version trunk => 2.40alpha r3
2008-06-19 11:29 plujan Status resolved => closed
2008-07-01 17:56 anonymous sf_bug_id 0 => 2007884


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker