Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0002038Openbravo ERP00. Application dictionarypublic2007-10-04 09:132008-06-12 09:43
Reporteriperdomo 
Assigned Torafaroda 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version2.40alpha-r2 
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
Summary0002038: Change the name of the an element in Price List Version
DescriptionEnvironment:
Database: Oracle
Version: R2.34


Go to:
1. Master Data Management > Pricing > Price List
2. Select a Price List
3. Go to the 'Price List Version' tab
4. You have a 'Price List Adjustment' field that must be renamed to 'Price List Schema'
Steps To Reproduce
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange

Notes
(0005627)
user71   
2005-06-01 00:00   
(edited on: 2008-06-12 09:43)
This bug was originally reported in SourceForge bug tracker and then migrated to Mantis.

You can see the original bug report in:
https://sourceforge.net/support/tracker.php?aid=1807332 [^]
(0002281)
rafaroda   
2007-10-25 09:15   
(edited on: 2008-06-12 09:22)
Logged In: YES
user_id=1892190
Originator: NO

Verification assigned to rafaroda.
(0002282)
rafaroda   
2007-10-25 10:31   
(edited on: 2008-06-12 09:22)
Logged In: YES
user_id=1892190
Originator: NO

Name remains as 'Price List Adjustment' in R2.35.
(0002283)
rafaroda   
2008-01-10 14:14   
(edited on: 2008-06-12 09:22)
Logged In: YES
user_id=1892190
Originator: NO

Using Openbravo ERP, change 'Price List Adjustment' field name by 'Price List Schema' in 'Application Dictionnary > Windows, tabs and fields' (Window: Price List - Tab: Price List Version - Field: Price List Adjustment) and then perform an 'export.database' to reflect the change in 'database/sourcedata/AD_FIELD.xml' file.