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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0014033
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] 07. Sales managementminoralways2010-07-22 12:202010-08-19 00:00
ReporternetworkbView Statuspublic 
Assigned Toadrianromero 
PriorityhighResolutionsuspendedFixed in Version
StatusclosedFix in branchpiFixed in SCM revision
ProjectionnoneETAnoneTarget Version2.50MP21
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product Version2.50MP19SCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0014033: The Address field keeps the value of the previous invoice

DescriptionThe Address field keep the value of the previous invoice. This error happens in Firefox.
Steps To Reproduce- Go to Sales Management || Transactions || Sales Invoice
- Create a new record (BP: McGiveer)
- Save and new.
- Realize that the Address field keeps the last value (talavera de la Reina...)
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0029952)
adrianromero (manager)
2010-08-13 13:22

To fill the locations list an SQL sentence is executed, and this sentence needs the Business Partner as a parameter

The error is in the code line https://code.openbravo.com/erp/devel/pi/file/3d3e7ced4ea6/src/org/openbravo/erpCommon/utility/Utility.java#l1378 [^] when reading the Business Partner ID parameter. Because the value is empty in the window then it is read from the session, and because the Business Partner ID is marked as stored in session and session values are not cleaned when pressing new, the list is filled incorrectly with the locations of the latest Business Partner.

The problem here is that all the behaviors described that are the cause of the error cannot be modified easily without breaking any other part of the application and raising several regression issues.
(0030113)
adrianromero (manager)
2010-08-18 13:10

All the possible solutions explored break the current functionality or are very risky.

* Removing the "In session" attribute of the Business Partner field is risky because this value is used in other parts of the window.
* Removing the validation of the locator field and let the callout fill in the locator does not work because the application will fill the field with all possible values.
* To hide the locator field when the business partner is empty does not have functional explanation and breaks the current behavior of the application.
* To change the behavior of functions in the Utility.java class is very risky because problems will appear in other parts of the application

- Issue History
Date Modified Username Field Change
2010-07-22 12:20 networkb New Issue
2010-07-22 12:20 networkb Assigned To => adrianromero
2010-07-22 17:01 adrianromero Status new => scheduled
2010-07-22 17:01 adrianromero fix_in_branch => pi
2010-08-13 13:22 adrianromero Note Added: 0029952
2010-08-18 13:10 adrianromero Note Added: 0030113
2010-08-18 13:10 adrianromero Status scheduled => closed
2010-08-18 13:10 adrianromero Resolution open => suspended
2010-08-19 00:00 anonymous sf_bug_id 0 => 3048129


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker