[
https://issues.apache.org/jira/browse/OFBIZ-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anil K Patel resolved OFBIZ-2942.
---------------------------------
Resolution: Fixed
Thanks Adam Heath for reporting the issue. The patch by Deepak Dixit on Jira
ticket fixes the issue. Now fromDate is also an IN parameter, if found null,
then default to now timestamp.
Fix applied to trunk and 13.07 branch.
> createPartyContactMechPurpose service doesn't allow fromDate
> ------------------------------------------------------------
>
> Key: OFBIZ-2942
> URL: https://issues.apache.org/jira/browse/OFBIZ-2942
> Project: OFBiz
> Issue Type: Bug
> Components: party
> Affects Versions: Release Branch 4.0, Release Branch 09.04, Trunk
> Reporter: Adam Heath
> Assignee: Anil K Patel
> Attachments: OFBIZ-2942.patch
>
>
> createPartyContactMechPurpose service doesn't allow the fromDate to be
> specified; in the java code, it is hard-coded to always call
> UtilDateTime.nowTimestamp().
> I've got an importer, that does a lot of things. I save the current time at
> the start of the script, then use that same time in all parts, so that all
> the date filter is consistent. The above bug keeps me from having consistent
> data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
