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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0017859
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] A. Platformmajoralways2011-07-01 11:482011-07-06 02:42
ReporterpsarobeView Statuspublic 
Assigned Tomarvintm 
PriorityimmediateResolutionfixedFixed in Version
StatusclosedFix in branchFixed in SCM revision4524abe1b4e5
ProjectionnoneETAnoneTarget Version3.0MP1
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product Version3.0MP0SCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0017859: If you change the organization in the sales order once it is saved fails

DescriptionWhen you change the organization in a sales order that is already saved, you cannot the organization because it shows you an error message when saving it again. This is not correct. You should be able to save the record after changing the record
Steps To Reproduce1. Go to sales order
2. Click new and select US inc org
3. Select a business partner and save
4. Change the org to EspaƱa
5. Change the business partner and save

You will see the error message.

TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0038670)
hgbot (developer)
2011-07-01 12:55

Repository: erp/devel/pi
Changeset: 4524abe1b4e564e48d08d93ee1b27263c85a5654
Author: Antonio Moreno <antonio.moreno <at> openbravo.com>
Date: Fri Jul 01 12:54:35 2011 +0200
URL: http://code.openbravo.com/erp/devel/pi/rev/4524abe1b4e564e48d08d93ee1b27263c85a5654 [^]

Fixed issue 17859. Changing org and bp in sales order will no longer prevent the user from saving.
The problem was that the business partner callout provided new values for the sales representative combo. This combo, as it is related to a non mandatory column, should have an initial blank value, which should be automatically selected as the callout logic doesn't provide a selected value. However, the FIC didn't add a blank element in this case.
The change has been to add this blank value in case of non mandatory column, and to automatically select it in case no selected value is provided.

---
M modules/org.openbravo.client.application/src/org/openbravo/client/application/window/FormInitializationComponent.java
---
(0038780)
shuehner (administrator)
2011-07-05 13:52

Reviewed/tested on pi/pgsql/chromium (rev id: e3cd8b5b827c).commit message explain that it restores same behavior which was used in 2.50 assuming that is correct (as not defined anywhere) cset is implemented that behavior. Testing the usecase as provided in the issue is now not producing an error but lets you save the row after the specified changes (org or org+bpartner).
(0038846)
hudsonbot (developer)
2011-07-06 02:42

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/f1c481b1a146 [^]

Maturity status: Test

- Issue History
Date Modified Username Field Change
2011-07-01 11:48 psarobe New Issue
2011-07-01 11:48 psarobe Assigned To => marvintm
2011-07-01 11:48 psarobe Modules => Core
2011-07-01 12:55 hgbot Checkin
2011-07-01 12:55 hgbot Note Added: 0038670
2011-07-01 12:55 hgbot Status new => resolved
2011-07-01 12:55 hgbot Resolution open => fixed
2011-07-01 12:55 hgbot Fixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/4524abe1b4e564e48d08d93ee1b27263c85a5654 [^]
2011-07-05 13:52 shuehner Note Added: 0038780
2011-07-05 13:52 shuehner Status resolved => closed
2011-07-06 02:42 hudsonbot Checkin
2011-07-06 02:42 hudsonbot Note Added: 0038846


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker