Skip to main content
Solved

Dropdown value sync between BigCommerce and Acumatica does not match


We are trying to sync modifier options from BigCommerce to Acumatica. However, when the modifier type is ‘dropdown’ the value that syncs over to Acumatica does not match BigCommerce. 

 

If we have the modifier type set to a text field, then the value syncs over just fine. but we need it to be a dropdown option, and would appreciate any insight into how to get the value to sync over correctly

Best answer by rakeshe45

Hi ​@dmccoy12 

We verified below mapping and it is working as expected. Can you try the same.

Size.DisplayValue 

 

View original
Did this topic help you find an answer to your question?

5 replies

davidnavasardyan
Jr Varsity I
Forum|alt.badge.img+3

Hi ​@dmccoy12 

This usually happens when the BigCommerce dropdown option value (the label shown to customers) doesn’t match the internal value being passed through the API. Acumatica might be getting the internal option ID or value instead of the display text. To fix it, check your BigCommerce modifier setup — make sure the option values have both a label and a unique value, and ensure those are mapped correctly in the Acumatica connector settings or customization. You may need to customize the sync to pull the display label instead of the raw value.


  • Author
  • Freshman I
  • 2 replies
  • April 15, 2025
davidnavasardyan wrote:

You may need to customize the sync to pull the display label instead of the raw value.

Thanks, this is what we were thinking since we have tried different ways to get the sync over and have been unsuccessful. appreciate the insight


Forum|alt.badge.img+1

Hello ​@dmccoy12 

 Can you map Size.DisplayValue in the ExternalField/Value and try once. Hope this works.

For more details, please refer to the BigCAPI call portal:

https://developer.bigcommerce.com/docs/rest-management/orders/order-products

Thanks,


Forum|alt.badge.img
  • Jr Varsity III
  • 14 replies
  • Answer
  • April 16, 2025

Hi ​@dmccoy12 

We verified below mapping and it is working as expected. Can you try the same.

Size.DisplayValue 

 


  • Author
  • Freshman I
  • 2 replies
  • April 16, 2025
rakeshe45 wrote:

Hi ​@dmccoy12 

We verified below mapping and it is working as expected. Can you try the same.

Size.DisplayValue 

 

That was it! thanks so much for the help. confirmed it worked. appreciate the help!


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings