The following are three things that I have added to my import routine in Acumatica. I find that, even though these are very simple things, they help to save time and headaches.
1. Create and map columns in your data for all fields that you may affect even if it is not a part of your next import
It is important on the initial data import to include all fields that you may import values for now or in the future. I find that having all the fields available for mapping is better than getting to the mapping stage and not being able to because the field was not included as part of the data schema in the data provider. This will save you from having to go back create a new data provider just to include the new field.
2. If changes are made to values directly within Acumatica when troubleshooting import errors, remember to repeat those changes in your source data
Sometimes when I am confident that there are little or no errors in the source file, I let the import run while the “Break on Error” checkbox is enabled. Sure enough, there are usually a couple formatting errors that I must deal with. In this instance, rather than making the changes in the source file and re-uploading the file, I just make the necessary change directly in the import scenario in Acumatica. When I do this, I don’t need to prepare the file again. I just hit import and the import continues from where it left off. This saves time on import, but it is also necessary for me to remember to make that change in the source file and re-upload when I have a chance. Otherwise, if I try to update and the column that had the formatting error is included, I will run into the same error. I try to keep the source file free from errors in case I need to update.
3. Ensure all columns in your source file are formatted as text
There have been many times that I encountered errors while importing and could not find the problem. I check and recheck the data and the input sequence and cannot find the issue. I have learned to format the whole source file as text and re-upload when this happens. Then, when I attempt to import again, there is no longer an error. When a column in your source file is not formatted as text you will not be able to import so formatting as text usually solves the problem.
MIBAR is a leading Acumatica Partner in New York. Sold only through a selective network of implementation partners like MIBAR, you can trust that you’re getting not only the technology you need, but the service and support you deserve. Contact us today to learn more.
Additional Acumatica Resources
Acumatica: How to Remove the Footer URL on an Invoice
Acumatica Cloud ERP: Creating Dashboards With Less Maintenance
