You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "HotWax Media OFBiz Team (JIRA)" <ji...@apache.org> on 2014/08/16 13:29:18 UTC
[jira] [Commented] (OFBIZ-5654) Updating custom time period
generates error
[ https://issues.apache.org/jira/browse/OFBIZ-5654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14099603#comment-14099603 ]
HotWax Media OFBiz Team commented on OFBIZ-5654:
------------------------------------------------
To make the string parsable, changed the format of the string to "yyyy-MM-dd". Now it becomes consistent with the "set as current" screen. Also corrected the value of customTimePeriodId.
> Updating custom time period generates error
> --------------------------------------------
>
> Key: OFBIZ-5654
> URL: https://issues.apache.org/jira/browse/OFBIZ-5654
> Project: OFBiz
> Issue Type: Bug
> Components: accounting
> Affects Versions: Trunk
> Reporter: Pierre Smits
> Assignee: Jacopo Cappellato
>
> When updating a custom time period in the overview of the time periods accounting - edit custom time periods following error is shown:
> The Following Errors Occurred:
> Type conversion of field [fromDate] to type [java.sql.Date] failed for value "Jan 1, 2010": org.ofbiz.base.util.GeneralException: java.text.ParseException: Unparseable date: "Jan 1, 2010" (java.text.ParseException: Unparseable date: "Jan 1, 2010")
> Type conversion of field [thruDate] to type [java.sql.Date] failed for value "Apr 1, 2010": org.ofbiz.base.util.GeneralException: java.text.ParseException: Unparseable date: "Apr 1, 2010" (java.text.ParseException: Unparseable date: "Apr 1, 2010")
--
This message was sent by Atlassian JIRA
(v6.2#6252)