Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0016399Openbravo ERPB. User interfacepublic2011-03-21 12:032011-04-06 00:00
Reporterplujan 
Assigned Tomtaal 
PrioritynormalSeveritymajorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Versionpi 
Target Version3.0RC6Fixed 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
Summary0016399: Price List Version is filled with wrong values if date format is not default
DescriptionI have dd/mm/yyyy as date format (slash instead of hyphen as separator). When creating a Price List, the Price List Version is filled with a value that is not correct comparing to the one used when hyphen is the separator. See steps.
Steps To Reproduce1. Use a context having Openbravo.properties modified to these values:
    dateFormat.js=%d/%m/%Y
    dateFormat.sql=DD/MM/YYYY
    dateFormat.java=dd/MM/yyyy
    dateTimeFormat.java=dd/MM/yyyy HH:mm:ss
    dateTimeFormat.sql=DD/MM/YYYY HH24:MI:SS
2. Log in as QAAdmin
3. Go to Price List and create a record filling all the mandatory values.
4. Save and move to Price List Version.
5. Click in New. The Name field is filled with a wrong value. See screenshot 1
6. Use a context with default values (dd-mm-yyyy) and repeat the steps. Now the value filled is the correct one. See screenshot 2
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to defect 0036897 closed jarmendariz Different types of date format when using the @#Date@ default value into a String reference 
Attached Filespng screenshot-44.png (36,209) 2011-03-21 12:03
https://issues.openbravo.com/file_download.php?file_id=3720&type=bug
png

png screenshot-45.png (39,942) 2011-03-21 12:03
https://issues.openbravo.com/file_download.php?file_id=3721&type=bug
png
Issue History
Date ModifiedUsernameFieldChange
2011-03-21 12:03plujanNew Issue
2011-03-21 12:03plujanAssigned To => mtaal
2011-03-21 12:03plujanFile Added: screenshot-44.png
2011-03-21 12:03plujanModules => Core
2011-03-21 12:03plujanFile Added: screenshot-45.png
2011-03-21 12:09psarobeStatusnew => scheduled
2011-03-21 12:09psarobeTarget Version => 3.0RC6
2011-04-04 17:06mtaalAssigned Tomtaal => marvintm
2011-04-04 17:07mtaalAssigned Tomarvintm => mtaal
2011-04-04 18:58hgbotCheckin
2011-04-04 18:58hgbotNote Added: 0035572
2011-04-04 18:58hgbotStatusscheduled => resolved
2011-04-04 18:58hgbotResolutionopen => fixed
2011-04-04 18:58hgbotFixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/19eaac5626ce6f11f46439091788a1989538ba06 [^]
2011-04-05 16:52mtaalNote Added: 0035622
2011-04-05 16:52mtaalStatusresolved => closed
2011-04-06 00:00anonymoussf_bug_id0 => 3276666
2017-11-24 09:42caristuRelationship addedrelated to 0036897

Notes
(0035572)
hgbot   
2011-04-04 18:58   
Repository: erp/devel/pi
Changeset: 19eaac5626ce6f11f46439091788a1989538ba06
Author: Antonio Moreno <antonio.moreno <at> openbravo.com>
Date: Mon Apr 04 18:41:52 2011 +0200
URL: http://code.openbravo.com/erp/devel/pi/rev/19eaac5626ce6f11f46439091788a1989538ba06 [^]

Fixed issue 16399. Date defaults will be set differently so they don't require a date reference.
Two changes have been done:
- In the UIDefinition, if the default is '@#Date', we will first check if the UIDefinition is a Date one, and if not, we will find one that is. Then, we will use its specific methods to correctly parse the date into a correctly defined date.
- In the UI, if the column value has 'hasDateDefault' set, then we will use the classic value (which has the nice looking date, instead of the JSON one)

---
M modules/org.openbravo.client.application/web/org.openbravo.client.application/js/ob-view-form.js
M modules/org.openbravo.client.kernel/src/org/openbravo/client/kernel/reference/UIDefinition.java
---
(0035622)
mtaal   
2011-04-05 16:52   
Works