Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0010205 | Openbravo ERP | A. Platform | public | 2009-08-06 13:35 | 2011-11-24 14:56 |
|
Reporter | nataliaperu | |
Assigned To | jonalegriaesarte | |
Priority | urgent | Severity | major | Reproducibility | always |
Status | closed | Resolution | no change required | |
Platform | | OS | 5 | OS Version | |
Product Version | 2.50MP3 | |
Target Version | | Fixed in Version | | |
Merge Request Status | |
Review Assigned To | |
OBNetwork customer | |
Web browser | |
Modules | Core |
Support ticket | |
Regression level | |
Regression date | |
Regression introduced in release | |
Regression introduced by commit | |
Triggers an Emergency Pack | No |
|
Summary | 0010205: SL_Order_Doctype returns non translated values |
Description | In Sales Order, when POS order is selected (working in other language than English), non-translated invoice terms are returned.
We are working in Spanish, but those names are in English.
SL_Order_Doctype is executed when a document type is selected, so it is not working properly. |
Steps To Reproduce | Install Spanish language.
Go to Sales management > Transactions > Sales Order.
Create a new order and select as Transaction Document POS Order (Pedido Punto de venta).
See that Invoice terms are not translated. |
Proposed Solution | |
Additional Information | |
Tags | No tags attached. |
Relationships | related to | defect | 0000570 | | closed | gorkaion | TST240r2: POS order cannot be completed |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2009-08-06 13:35 | nataliaperu | New Issue | |
2009-08-06 13:35 | nataliaperu | Assigned To | => rafaroda |
2009-08-31 10:42 | rafaroda | Relationship added | related to 0010319 |
2009-08-31 10:43 | rafaroda | Note Added: 0019321 | |
2009-08-31 10:43 | rafaroda | Assigned To | rafaroda => alostale |
2009-08-31 10:43 | rafaroda | Priority | normal => urgent |
2009-08-31 10:43 | rafaroda | Severity | minor => major |
2009-08-31 10:43 | rafaroda | Status | new => scheduled |
2009-08-31 10:43 | rafaroda | Category | 07. Sales management => A. Platform |
2009-08-31 10:46 | rafaroda | Note Added: 0019322 | |
2009-09-23 12:12 | shuehner | Note Added: 0020308 | |
2009-09-23 12:13 | shuehner | Relationship deleted | related to 0010319 |
2009-09-23 12:13 | shuehner | Relationship added | related to 0000570 |
2009-09-23 12:15 | shuehner | Assigned To | alostale => rafaroda |
2010-02-11 18:05 | rafaroda | Assigned To | rafaroda => adrianromero |
2011-06-03 11:00 | dalsasua | Assigned To | adrianromero => dalsasua |
2011-07-20 18:11 | dalsasua | Assigned To | dalsasua => jonalegriaesarte |
2011-11-24 14:56 | jonalegriaesarte | Note Added: 0043165 | |
2011-11-24 14:56 | jonalegriaesarte | Status | scheduled => closed |
2011-11-24 14:56 | jonalegriaesarte | Resolution | open => no change required |
Notes |
|
|
Asier,
Please close this issue if it is duplicated of 0010319
Thanks. |
|
|
|
SELECT RE.NAME AS REFERENCE, REL.NAME AS EN, RELT.NAME AS ES
FROM AD_REFERENCE RE, AD_REF_LIST REL, AD_REF_LIST_TRL RELT
WHERE RE.AD_REFERENCE_ID = REL.AD_REFERENCE_ID
AND REL.AD_REF_LIST_ID = RELT.AD_REF_LIST_ID
AND RELT.AD_LANGUAGE = 'es_ES'
AND UPPER(RE.NAME) LIKE '%INVOICERULE%'
ORDER BY REFERENCE |
|
|
|
@Rafa: this is unrelated to 10319 and the problem was introduced much earlier.
Issue 570: pristine/pi commit 14444
Added extra code for 'POS Order' part of the code uses ComboTableData to fill in the values (should have translations right automatically) however another part of the code (lines 182-192) just calls ListData.selectName instead of ListData.selectNameTrl and thus completely ignores translations.
Note: the same/similar problem seems to be in SL_Invoice_DocType (line 99)... and perhaps in more places in both files.
So not a platform issues just broken callout implementation. |
|
|
(0043165)
|
jonalegriaesarte
|
2011-11-24 14:56
|
|
Openbravo provides community support only for the latest Openbravo version, which is Openbravo 3. This version has significantly improved financial flow, filtering, performance, etc and this issue is not present there. Upgrade path from Openbravo 2.50 to latest Openbravo version is available so we recommend to upgrade your instance to get this issue fixed.
Life cycle guarantee (backporting bug fixes to the previos to latest releases (Openbravo 2.40, 2.50)) is available for Professional Edition subscribers only. Please register your ticket through Openbravo Support Portal (http://support.openbravo.com/ [^]) if you have valid Professional subscription.
You can find more details about our Support policy in the following blog post
http://paolojuvara.blogspot.com/2009/12/maintenance-policy-for-openbravo-250.html [^] |
|