[
https://issues.apache.org/jira/browse/OFBIZ-10588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17032379#comment-17032379 ]
ASF subversion and git services commented on OFBIZ-10588:
---------------------------------------------------------
Commit 2f479d56ce7b715961ba2fa1b67362b13351ebcb in ofbiz-framework's branch refs/heads/release17.12 from Jacques Le Roux
[
https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=2f479d5 ]
Fixed: Unable to continue to Step 3 in One Page Checkout
(OFBIZ-11318)
The following error is returned when trying to continue to Step3 when checking
out using One Page Checkout.
Could not create new purpose, a purpose with that type already exists.:
[GenericEntity:PartyContactWithPurpose][contactFromDate,2020-01-05 19:48:18.29
(java.sql.Timestamp)][contactMechId,10020(java.lang.String)]
[contactMechPurposeTypeId,SHIPPING_LOCATION(java.lang.String)]
[partyId,admin(java.lang.String)][purposeFromDate,2020-01-05 19:48:18.332
(java.sql.Timestamp)
It does not happen with DemoCustomer but at least with admin user
It was caused by OFBIZ-10588. I checked for similar issues and found that, in
unlike in createUpdateBillingAddress, in createUpdateShippingAddress and
createUpdateCreditCard partyId was used without a prior setting from
parameters.partyId
Thanks: James Young for proposing a solution. I rather fixed otherwise this and
another similar case in createUpdateCreditCard
> Incorrect PartyContactMechPurpose created while calling createUpdateBillingAddress service
> ------------------------------------------------------------------------------------------
>
> Key: OFBIZ-10588
> URL:
https://issues.apache.org/jira/browse/OFBIZ-10588> Project: OFBiz
> Issue Type: Bug
> Components: order
> Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12
> Reporter: Suraj Khurana
> Assignee: Suraj Khurana
> Priority: Major
> Fix For: 17.12.01, 16.11.06
>
> Attachments: OFBIZ-10588.patch
>
>
> createUpdateBillingAddress and createUpdateShippingAddress services create incorrect PartyContactMechPurpose records with userLogin.partyId.
> These services works well in case of when e-commerce logged-in user perform these operation. But in-correct data is created by these services if called from admin or any other user.
> Need to check relevant code and fix it.
> I called createUpdateBillingAddress service from webtools and and didn't get desired results.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Locked
