search

classyllama / ClassyLlama_AvaTax

This extension has been deprecated in favor of https://github.com/avadev/Avalara-AvaTax-for-Magento2
Open Software License 3.0
23 stars 15 forks source link

Billing Address Changes to Shipping Address when "Same as Billing" checked After Validating (On frontend) #221

Closed joshuaqueenava closed 5 years ago

joshuaqueenava commented 5 years ago

{}Account Name:{} {}Account Number(s):{} {}Company Code(s):{} 3872663 {}AvaTax Environment:{} PROD {}ERP Version:{} Magento 2.2.4 Community - AvaTax 1.5.0 {}AvaTax Integration Version:{} {}AvaTax Adapter Version:{} 15.5.1.0 {}OS/Browser Version:{} Chrome {}Repro Frequency{} ALL

{}Description:{} We are experiencing an issue on our checkout page at where if the client ha a different billing address other than the shipping address and tries to input the new address, Avatax reverts the new billing back to the shipping address because of the Address Validation setting in the config feel for your module in Magento 2.

Once we disable this option >>> Address Validation The checkout works as it should be.

Can we install a third party address verification module to handle this or is there a better solution on your end.

We’ve updated the module to your latest version and we are still receiving the same error. Please advise.

{}Steps to Reproduce:{} See above

{}Expected Result:{} Expects the address entered to be the one that is used for calculation

{}Actual Result:{} The system ins reverting the billing address back to the shipping address

{}Attachments/Documentation:{}

joshuaqueenava commented 5 years ago

Video recording of issue.

https://avalara1-my.sharepoint.com/:v:/g/personal/joshua_queen_avalara_com/ER19iPUtDhdAgH7lcKNqWNQBOP8lu_AW-kBZkc-svvFT7Q?e=Ug9At6

joshuaqueenava commented 5 years ago

Has there been any analysis on this issue? Customer is requesting an update. Thank you.

prestonchoate commented 5 years ago

@joshuaqueenava Sorry I missed this one. I haven't yet done any analysis on it. I will open an internal ticket so this can be investigated next week.

prestonchoate commented 5 years ago

@joshuaqueenava This customer is utilizing a custom one step checkout that is most likely causing this issue. I have been speaking with them via email and have informed them of the situation.