Skip to content
This repository has been archived by the owner on Apr 22, 2019. It is now read-only.

Duplicate Address Entities Created #115

Closed
rsisco opened this issue Mar 12, 2018 · 5 comments
Closed

Duplicate Address Entities Created #115

rsisco opened this issue Mar 12, 2018 · 5 comments
Assignees

Comments

@rsisco
Copy link

rsisco commented Mar 12, 2018

When AvaTax address validation is enabled, if a customer with no saved addresses checks out using the same address for billing and shipping, the result will be the creation of two separate (but identical) address entries for the customer.

Preconditions

  1. Magento 2.x
  2. AvaTax extension is installed with address validation enabled

Steps to reproduce

  1. Create a new customer account, but do not add any addresses to the account
  2. Add item(s) to cart and proceed to checkout
  3. Provide a shipping address and allow Magento to use the same address for billing
  4. Place order

Expected result

  1. A single address entry will be created for the customer

Actual result

  1. The provided address is saved twice, as two separate address entities; once as the default shipping address and once as the default billing address.
    img
  2. This results in the availability of two identical address choices when the customer checks out with their next order.
    img
@rsisco rsisco self-assigned this Mar 12, 2018
@VolodymyrEl
Copy link

VolodymyrEl commented Mar 17, 2018

@rsisco
Copy link
Author

rsisco commented Mar 19, 2018

@VolodymyrEl - I have not had the opportunity to start digging into this yet. If you have the ability to create a solution, feel free to submit a PR back to the repo and we will review and include your changes in the codebase as appropriate.

@parththummar
Copy link

Any update on this? we are also facing the same issue.

@rsisco
Copy link
Author

rsisco commented Apr 9, 2018

@parththummar - The issue is being investigated, but we do not yet have a fix.

@rsisco
Copy link
Author

rsisco commented Oct 25, 2018

This issue has been addressed in release #1.4.9. Closing issue.

@rsisco rsisco closed this as completed Oct 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants