I noticed this behavior as of at least 24R2. When you map a field in Acumatica to be a custom field in BigC, the connector will create the custom field in BigC only if that field has a value in Acumatica. Previously when we were on 23R1, if you deleted the text from the field in Acumatica, on the next sync, the custom field would be deleted in BigCommerce. Now as of 24R2, previously created custom fields are not being deleted from BigCommerce when they are given an empty value in Acumatica. Instead the custom fields in BigC retain the last value that was in Acumatica before it was deleted. This seems like a bug to me and is very inconvenient for us. Has anyone else experienced this and found a solution?
Question
BigCommerce Custom Fields Syncing Bug
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.