@lawsont - sounds like it is only useful for orders entered directly within Acumatica, unfortunately.
@KarthikGajendran we have recently started experiencing the same issue.Is the suggested solution to delete the phone number from the customer record in Acumatica and then resync? Because while that allows the records to sync, in my testing the phone number remains deleted in the customer record in Acumatica (instead of reimporting from the corresponding customer record in Shopify).
@KarthikGajendran I tried resyncing that customer record several times after removing the phone number in Acumatica and it never reimported from the customer record.
@MComan62 - yes, the ARTran table only includes data for sales orders that have shipped and been invoiced so you’ll need to substitute the SOOrder table (twice) instead of the ARTran table(s). That will get you all order data (including orders in Awaiting Payment status).
@BorisRudi56 - I see that build 23.208.0026 is now available. Can you confirm that this issue was fixed in this build? I didn’t see any mention of it in the release notes. And if it has not yet been fixed, can you advise when it will be fixed?
@simonliang91 - we’ve been preparing to upgrade from 23R1 to 23R208 for this specific fix. Do you have any general idea when 23R209 will be released?
Great! Thanks, @simonliang91
@kyle90 - you’re right, that is no longer working for us after upgrading to 23R1. @Kandy Beatty - do you have any similar solutions for use in 23R1 and above? Or is the discount the only other option?
@kyle90 - looks like this article provides some more options: We’ll probably use Option 1 ourselves as it seems to keep all of the old functionality regarding tying to the correct GL accounts:
Confirming this is working in 23.210.0017!
@simonliang91 - I updated my comment right after I posted it; just had to tweak the mapping and then it worked. Thanks!
@bcameron - not 100%, no. I think we’re about 80-90% there. What I did was I created an attribute that I added as a User Defined Field on the Customer record: We’re now using this to designate an “account manager” for the entire customer record/account. I then created a GI that referenced this field and all of the customer locations and built a business event with an import scenario to update all of the customer’s locations with the value set in this “account manager” UDF when they don’t match. This works fairly well.The one thing I haven’t been able to solve is when a customer creates a new location in Shopify and that syncs over to Acumatica; these don’t seem to trigger the business event. So I created a separate, manual import scenario on an automation schedule to catch any of these throughout the day.This is the best I’ve been able to come up with short of a customization to the connector, which I’m hesitant to do.
Already have an account? Login
Enter your 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.