Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0008309Openbravo ERP07. Sales managementpublic2009-03-26 13:222009-04-29 00:00
Reporterpsarobe 
Assigned Toshuehner 
PriorityhighSeverityminorReproducibilityalways
StatusclosedResolutionopen 
PlatformOS5OS Version
Product Versionmain 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0008309: Error message not parsed in postgres. Sales order window
DescriptionError message not parsed in postgres. Sales order window
Steps To Reproduce1. Go to Sales management->Transactions->Sales order-> Header
2. Select Mafalda and warehouse order transaction type. Save
3. Move to lines and select Shirts and click the attribute selector. Select Medium
4. Move back to header and complete

You will the message
Proposed Solution
Additional Information
Tags250MP1
Relationships
related to defect 00003152.40 closed cromero AT235mp4 - On PostgreSQL, when I try to complete a Sales Order, I get an error 
related to defect 0008477 closed vinothbabu Without Locator error occurs while Completing Sales Order 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-03-26 13:22psarobeNew Issue
2009-03-26 13:22psarobeAssigned To => shuehner
2009-03-26 13:22psarobeRegression testing => No
2009-03-26 13:22psarobeStatusnew => scheduled
2009-03-26 13:22psarobefix_in_branch => pi
2009-04-21 11:13shuehnerRelationship addedrelated to 0000315
2009-04-21 11:14shuehnerNote Added: 0015472
2009-04-23 16:05psarobeTag Attached: 250MP1
2009-04-27 16:57shuehnerNote Added: 0015808
2009-04-27 16:57shuehnerStatusscheduled => feedback
2009-04-27 17:01rafarodaRelationship addedrelated to 0008477
2009-04-28 13:56psarobeStatusfeedback => closed
2009-04-28 13:56psarobeNote Added: 0015853
2009-04-29 00:00anonymoussf_bug_id0 => 2783255

Notes
(0015472)
shuehner   
2009-04-21 11:14   
Added related to, with an old issue which introduced the change which produces the broken error message.
(0015808)
shuehner   
2009-04-27 16:57   
Not reproducible anymore. Most likely this is fixed with the change in issue 8477, which did modify the part which did cut the error message into pieces. please retest in current pi.
(0015853)
psarobe   
2009-04-28 13:56   
Stefan, you are right