Thank you @tusharpandita74 . Looking forward for the fixes.
Hi everyone,Just to provide update. We’ve been blocked by nested hierarchy of Sales Categories as it syncs only the immediate category of the item, and we are missing the Parent category. Also, child category name may exists also to other parent category. Example, a child category of Formal Attire that is under both Men and Women category.We end up combining the parent and child category name within the data, then synced it as tag. Then in Shopify, we create an automated collection to set rules for that.This is our solution for now for nested item sales categories. If there is better solution, please let me know. Thank you :)
Thank you for your answers @lawsont @jfarrell . Both make sense. I’ll try your recommendations.
@Yuri Karpenko , did I get this correctly? Tried simplifying the mapping to validate if entity mapping overrides store’s settings.Unfortunately, I still encounter the error. This is in 23R2
@mikeho @K2a Sorry for the delay. We had this in 21R2 and 22R2 and then we removed it because of some bugs in the Shopify API for metafields. We were waiting for Shopify to fix it. Now we are pushing Shopify to fix it and they promised that they will. We are now planning to fix it in 23R2 but if you also need it in 23R1, then please let me know. Hi @KarthikGajendran - can we have the fix for 23R1?We would like also to ask, since 23R2 will be launched in the next month, is the fix included already? Thank you
Thank you @Yuri Karpenko for the suggestion opening the case. You too 100% accurately explained what our concern is. I noticed that updating posting class, lot/serial class or other Template details updates the matrix items when we hit the Update Matrix items. We are expecting should be the same case too for Description.
Hi @Chris Hackett ..We fix the provided scenario by manually modifying BigCommerce product to make sure that number of options and their values matches what is in Acumatica, and if necessary, to match also the number of variants and their SKU (since in our case, not every permutation of options are existing products)
Gotcha. Thank you for your responses. So, setting the Export to External in the Item Class level to false will be inherited by stock items with that item class. I think that will be helpful
@KarthikGajendran Sorry, I forgot to mention that we are using Import Scenario in Importing attribute and options as well as assigning them to matrix items. So the updating of variant options/name of the matrix item is not by updating the attributes value (though description can be updated), but instead by creating a new set of options and replacing the old attribute value in that matrix/stock item. Thus, in our sample, from colors Red, Green, Blue, we have now Red, Green, Blue, Rose, Navy Blue and Lime Green color options. But Red, Green and Blue should not be in used anymore.
Hi @KarthikGajendran , do we have now updates regarding BigCommerce connector fix for sort order for the variant options from item class?
Thank you for your response @manikantad18 . I don’t have the Item class summary save between the attribute updates before, and it will be same result for the error. Appreciate too sharing your Import Scenario XML, and I know it will work for a single attribute imported. But we need to have multiple attributes to be imported depending on the data. I mean, if we have Item Class having 3 attributes, it will create 3 variant attributes, if 1, then 1 attribute, all at one Import By Scenario.
Thank you @smarenich and @Yuri Karpenko. I agree. Appreciate you expanding these scenarios, and providing tips. Great help!
Thank you @laura01 for your response.. I think I figured-out the cause. It’s on the customization I published before(of BundleB2B). I unpublished it, and works again. Not sure if re-publishing it will cause again the error. We’ll know. Appreciated by the way your help
Thank you @smarenich
Thank you for that information @Naveen Boga
Thanks for the response @amajors . But @Jeff96 is correct. We need to move also the inventory from the original item to a new one.
I am sorry for the late response. Yes, it works! I’m glad I am able to pull my discounts thru GI and custom endpoint. But I am not sure why it does pull all records, instead of returning only those based on the parameter I set on the request body.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.