I have an import scenario that will create sales orders from files added to an FTP server. I can set up an automation schedule to run the import scenario (we need it to import multiple times a day), however it is unpredictable when new order files will be added to the FTP site and I don’t want the import scenario to run if a new file hasn’t been synchronized, otherwise it will create duplicate sales orders in Acumatica.
Anyone have any direction on the best way to go about this?
+6
You have a couple options:
If I understand your issue correctly, duplicate orders might be created because you have autonumbering turned on for this specific order type. If you could get away with the manual numbering, using the order number from your source system, that would take care of duplicate orders. In other words, if you have order ‘12345’ in the source file, and Acumatica would create an order with ‘12345’ order number, then the next time an import runs, it would update the existing order, and not create a duplicate.
If however, you need to use autonumbering for this orders, in the import scenario use, use this for the Order Nbr:
This way, Acumatica will first search for that original order number, and if it’s found, it will update the existing record.
Of course, if you utilize this approach, then one of the steps in your import scenario should be:
I hope this helps.
Hi
I found that I had to import the external site order ID into the Acumatica Order Nbr. field in order to get the import scenario to work (the autonumbering overrides this in the end). Are you suggesting I insert your Order Nbr. -> Customer Order Nbr. line below my Order Nbr. line in my screenshot above? Or replace it altogether? I’ve tried both and neither has worked.
+6
When you say it doesn’t work, what’s happening? Is it throwing an error? Or is it just duplicating the lines?
Thank you!
However, if I prepare and import the scenario again, now instead of creating a duplicate order it duplicates the lines on the same sales order. Per your previous comment, “Acumatica will first search for that original order number, and if it’s found, it will update the existing record.”, so it seems like this is the behavior you were expecting?
What I really need is for the import scenario to check if the order already exists and, if it does, do nothing (don’t create a duplicate order nor add duplicate lines to the existing order).
Have you tried changing the synch type in the import scenario to “incremental”? This will only import changed or new records. So if the old file is still present on the ftp site, it will not be imported into Acumatica.
Hi
If that isn’t possible, we were thinking on other ways to trigger the import scenario not necessarily on a schedule but on some other flag that we manage for when to trigger the import scenario. For example, if we monitored the ftp location of where the file will sit, and when there is an update or new file uploaded, we can hit a webhook within acumatica and store that in a custom table. then have a Business Event that will trigger when there are unprocessed files, which would then trigger the import scenario. It’s not ideal as i would have hoped there was a way to more simply handle this within acumatica, so wanted to get your thoughts on it before we decided on our approach.
many thanks in advance.
Hi
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
