Good day,I have another strange import scenario issue. Sometimes it works.Do I need to make sure the business account owner matches or if blank I need to add the salesperson. I have used it before and it worked perfectly. I am trying to update over 8000 locations in the Salesperson tab/ by location. It is fails or takes for had not update and referred me to the BA Profile. If I do one at time, I don’t get an error.Any suggestion on making work with large customers with lots of locations.Thank you.@Evan G

Solved

Customer Salesperson update

Forum|Forum|1 year ago
January 25, 2024
2 replies
200 views

E

EvanG
Varsity I

Good day,

I have another strange import scenario issue. Sometimes it works.

Do I need to make sure the business account owner matches or if blank I need to add the salesperson.
I have used it before and it worked perfectly. I am trying to update over 8000 locations in the Salesperson tab/ by location. It is fails or takes for had not update and referred me to the BA Profile.
If I do one at time, I don’t get an error.

Any suggestion on making work with large customers with lots of locations.

Thank you.

@Evan G

Best answer by wojtysiaks

For large import scenarios where I am updating records, I sometimes click the ‘commit’ box on the save line of the import scenario. This will create an ‘ERP Transaction’ for each line in the import because it will save each line, then treat the next line like a brand new record, but helps when one of the records for the same customer fails. That way, the ones that do succeed will update, then you can deal with only the failures in the end. You would never want to do this with importing a one to many record, such as new bills with many lines per bill, for example. This may not resolve your entire issue, but may make finding the ones that fail a little easier.

W

wojtysiaks
Jr Varsity III
Answer
Forum|Forum|1 year ago
January 26, 2024

For large import scenarios where I am updating records, I sometimes click the ‘commit’ box on the save line of the import scenario. This will create an ‘ERP Transaction’ for each line in the import because it will save each line, then treat the next line like a brand new record, but helps when one of the records for the same customer fails. That way, the ones that do succeed will update, then you can deal with only the failures in the end. You would never want to do this with importing a one to many record, such as new bills with many lines per bill, for example. This may not resolve your entire issue, but may make finding the ones that fail a little easier.