Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0017205Openbravo ERP07. Sales managementpublic2011-05-17 16:112011-05-26 07:44
ReporterRenateNieuwkoop 
Assigned Tomarvintm 
PriorityimmediateSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Versionpi 
Target Version3.0RC7Fixed in Version3.0RC7 
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
Summary0017205: Sales order does not display Invoice Terms field for Standard order
DescriptionWhen you enter the Sales Order screen and enter a new Sales order with type Standard Order, the field Invoice Terms is not selectable. I thought this was resolved with issue 16788, but apparantly that was not the same problem.

The work around is to change to a POS Order, then invoice terms then appears and then change the order type to Standard Order again. The Invoice terms field remains visible.
Steps To ReproduceGo to the Sales Order screen and enter a new record. The default is Standard order and the Invoice Terms are not visible.
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to defect 00167883.0RC7 closed marvintm Invoice terms is not shown in sales order window 
Attached Filespng 170511InvoiceTerms1.png (57,646) 2011-05-17 16:11
https://issues.openbravo.com/file_download.php?file_id=4027&type=bug
png
Issue History
Date ModifiedUsernameFieldChange
2011-05-17 16:11RenateNieuwkoopNew Issue
2011-05-17 16:11RenateNieuwkoopAssigned To => psarobe
2011-05-17 16:11RenateNieuwkoopFile Added: 170511InvoiceTerms1.png
2011-05-17 16:11RenateNieuwkoopModules => Core
2011-05-17 16:11RenateNieuwkoopOBNetwork customer => No
2011-05-17 17:20psarobeAssigned Topsarobe => iperdomo
2011-05-17 17:20psarobeStatusnew => scheduled
2011-05-17 17:20psarobeTarget Version3.0MP7 => 3.0RC7
2011-05-17 20:10iperdomoRelationship addedrelated to 0016788
2011-05-17 20:15iperdomoNote Added: 0037112
2011-05-17 20:15iperdomoAssigned Toiperdomo => marvintm
2011-05-18 09:51hgbotCheckin
2011-05-18 09:51hgbotNote Added: 0037119
2011-05-18 09:51hgbotStatusscheduled => resolved
2011-05-18 09:51hgbotResolutionopen => fixed
2011-05-18 09:51hgbotFixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/ead0927e415d36fb6fab3c5d1bff412e6f7205fc [^]
2011-05-18 12:21psarobeNote Added: 0037132
2011-05-18 12:21psarobeStatusresolved => closed
2011-05-18 12:21psarobeFixed in Version => 3.0RC7
2011-05-26 07:44hudsonbotCheckin
2011-05-26 07:44hudsonbotNote Added: 0037484

Notes
(0037112)
iperdomo   
2011-05-17 20:15   
The issue happens on NEW, due to computation of auxiliar-inputs twice, related to this code:

https://code.openbravo.com/erp/devel/pi/rev/a7235c01dfce [^]

A callout set a value of ORDERTYPE but the computation of aux-input again, resets to the value to empty.
(0037119)
hgbot   
2011-05-18 09:51   
Repository: erp/devel/pi
Changeset: ead0927e415d36fb6fab3c5d1bff412e6f7205fc
Author: Antonio Moreno <antonio.moreno <at> openbravo.com>
Date: Wed May 18 09:49:45 2011 +0200
URL: http://code.openbravo.com/erp/devel/pi/rev/ead0927e415d36fb6fab3c5d1bff412e6f7205fc [^]

Fixed issue 17205. Auxiliary Inputs will be recomputed before callouts.
This means that if a callout modifies an auxiliary input value, its execution will override the previously calculated value instead of being overwritten afterwards.

---
M modules/org.openbravo.client.application/src/org/openbravo/client/application/window/FormInitializationComponent.java
---
(0037132)
psarobe   
2011-05-18 12:21   
Fixed
(0037484)
hudsonbot   
2011-05-26 07:44   
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/728387046be6 [^]

Maturity status: Test