I’m running into an issue with updating Customer addresses with the updateCustomer mutation. The first time I call updateCustomer with addresses in the payload, it updates the Customer as expected, adding the address and setting as the default. However, if I run the mutation again with the exact sam…

Hi Thanks for flagging this issue! The team is currently aware of this behaviour. In the mean time the work around to for your expected functionality, the second call not removing the address, is to ensure you have the address id, of the address you would like to update in the input for the Custo…

Hi, Any update on this issue? It really is a problem to have to query and verify each client and their addresses in any update, especially for bulk updates, it makes the purpose of the bulk update useless.

The problem still persists. Also the the address id is already deprecated so we can’t use that as suggested.. to get around the issue. I ended up using REST API instead and it works well.

Hello, Is there any hope that this bug will be fixed soon? All our developments have been done in REST and we are in the process of switching over to bulk mutations. This malfunction calls our project into question. Thank you for the update, so that we can make the best decisions. Why does a repl…

I’ve found an acceptable workaround… The bug does not occur if the data changes. In the case where the new data is exactly the same, we have chosen to alternately feed the first name or the last name, with the value “first name + last name” and empty for the other field. If it helps other people …

@lizk Same issue using GraphQL Admin API 2024-04. Here’s a Loom showing the behaviour. On subsequent customerUpdate calls, the address gets removed and then re-added, each time having a different ID. https://www.loom.com/share/8bf9cf43c4ab4b62a2a2671b95a66585?sid=67495513-988d-4a20-b80e-7f33a20919…

Great find @Lishan ! It puzzles me that the solution proposed by @lizk is now deprecated and we’re actually reverting to REST… Isn’t Shopify wanting devs to adopt GraphQL?

this is not solved, can you change the status to not solved?

same issue here. @lizk do you have any updates?

Hi @victorvila , There’s no updates on this issue at this time. Though I can assure you that I have reached out to our developers again to ensure that issue is being investigated and worked on with the correct priority. That said due to the technical nature of issues such as these and the various p…

Multiple updateCustomer mutations with same "addresses" payload will remove address

Retired Boards Appdev Customers Discounts And Orders

emartinello June 14, 2023, 9:23am 3

Is the problem still not resolved? The ids are not present in the customer addresses, how can I update the addresses without risking deleting them?

Topic		Replies	Views
customerUpdate mutation deletes previously saved addresses Custom Storefronts	2	88	April 3, 2024
Getting error Address has already been taken when updating customer Customers Discounts And Orders troubleshooting	1	116	November 2, 2023
Hydrogen Customer Address Update Failed Custom Storefronts optimization , troubleshooting , Setting-Up	1	35	June 27, 2024
Change Customer default address using Graphql Shopify Discussion troubleshooting , apps	0	45	July 5, 2021
creating a customer doesn't initialize their address. Custom Storefronts	1	16	August 26, 2021

Multiple updateCustomer mutations with same "addresses" payload will remove address

Related topics