Product data changes not geting properly synced to Sanity if there's another product with same slug about hull

[ndimatteo]

@raqibnur please open a separate issue with more details about what you are experiencing, instead of commenting on other people's issues that are still open 🤘

[ansmlc]

I've managed to "remove" one of the duplicate products by hardcoding its ID to product-delete.js API:
stx = stx.patch('product-${specific-id}', (patch) => patch.set({ wasDeleted: true }))

The product is now marked as "removed" in Sanity but the document is still there, and still giving the same "slug in use" warning:

Because of this slug conflict error the client still can't publish the proper product.

Any idea what other patch or mutation would perhaps be more useful?

[ndimatteo]

Hey there @ansmlc by default Sanity checks for uniqueness on slug fields for documents.

This is why it's not updating anything in Sanity when the sync function occurs. You can actually see the error message after the sync starts in your first screenshot:

You'll need to either delete the previous documents (and remove all references to those elsewhere first), or you can try overriding the default validation for the product slug fields in your schema to allow it to create product documents with the same slug values.

Let me know if that helps! 🤘

[raqibnur]

is there any way to check the localhost sanity error log? mine is not syncing

[ansmlc]

@ndimatteo This has been resolved by rolling back to an older dataset backup and avoiding having same-slug documents.