Correct Customer Class Via Import Scenario

  • 9 July 2022
  • 4 replies

Userlevel 4
Badge +1
  • Jr Varsity III
  • 92 replies

Version: 2021R1

Hello, as many of us experience, the commerce connector will only allow 1 customer class on import.  This functionality is limiting.  So I wanted to use other fields in the customer record to update the customer class (dynamically). 

So the intention would be: 

  1. commerce connector imports customer from Shopify with Customer Class “K2TEST”.
  2. I build a GI that looks for all records with customer class “K2TEST”
  3. I create a data provider based on the Generic Inquiry noted above.
  4. I create an import scenario that uses the data provider noted above and has logic to look at an ATTRIBUTE on the customer record and map a new customer class “K2NEWCLASS” accordingly.
  5. I then schedule the import scenario to run from a Business Event or Schedule...making it AUTOMATED.

This scenario works with EXCEL as the data provider, but obviously that takes manual intervention to process.  But switching to the GI gives me the following error:  1 items have not been processed successfully. View name: BAccount.

Mainly I think the reason is that when I add the fields to identify the record it leaves the “customer id” field blank under “Source Field/Value”.   I have tried to put everything in there such as BAccountID, AcctCD but to no avail. 

Here is my GI with 1 record present:

Here is my data provider:

I have checked the “KEY” box for both baccount_acctCD and Baccount_BaccountID and neither works


Here is my import scenario (if I type in “Customer ID” in the ‘Source Field/Value’ it tells me the field doesn’t exist:

And here is my import by scenario with error:

Thanks all!


Best answer by Naveen Boga 10 July 2022, 05:54

View original

4 replies

Userlevel 7
Badge +18

Hi @K2a  Can you please share the XML format of your import scenario? 

Userlevel 4
Badge +1


Userlevel 7
Badge +18

Hi, @K2a  Thanks for sharing the file.

I have seen a couple of issues in your import scenario, please find the details below.

  1. Customer ID should be mapped with the Baccount_acctCD
  2. In the end we should Save the Customer document. Save command is missed.

I have created my GI and associated it with your import scenario and it worked well for me.

Please find the screenshots below for reference.




Userlevel 4
Badge +1

@Naveen Boga thanks so much! I guess I was too busy to notice that I had dropped the “save” action off of it.  I had it there on a previous iteration.

Happy to say your solution worked!

I appreciate your help.





About Acumatica ERP system
Acumatica Cloud ERP provides the best business management solution for transforming your company to thrive in the new digital economy. Built on a future-proof platform with open architecture for rapid integrations, scalability, and ease of use, Acumatica delivers unparalleled value to small and midmarket organizations. Connected Business. Delivered.
© 2008 — 2024  Acumatica, Inc. All rights reserved