Sage 100

I have a feeling there is already a thread on this but I've searched and not found it. We recently upgraded a client from 2013 to 2017. they have always imported transactions into A/P invoice data entry. Since the upgrade the users have accidentally imported invoices a second time (after the first run was updated) and Sage posted the second run as an adjustment. Essentially the A/P invoices were now doubled. They tell me in the prior version, that if they ran the import for the same invoices, those records would fail during the VI import and that would be their alert that they were importing the same file again. I can write perform logic to rename their file after the import and that should alleviate their issue, but is there something that can be done to trigger the records to fail during import if someone would re-import an existing A/P invoice? The only thing I've found on Sage's website does not seem very helpful. (below) **Duplicate Accounts Payable invoice numbers are allowed during by Visual Integrator importing Disclaimer Support Sage Customer Support does not provide assistance for issues related to third party products or enhancements, hardware, report customizations, state or federal tax-related questions, or specific accounting questions. Please contact your Sage business partner, network administrator, or accountant for assistance. Please review this document for additional information on the scope of Sage Customer Support Services. Resolution Manual entry does generate a duplicate invoice warning ""Invoice number already on file"". Visual Integrator does not contain perform logic to check for duplicate invoice numbers in history. This would require custom Perform logic to be created by a 3rd party Master Developer. Please check with your business partner, reseller, or Master Developer for customizations.**

David - Here on SocialCast (somewhere) I posted the original Perform Logic myself for our beloved @JimWoodhead for versions 4.40 and 4.30. The 4.40 version works thru v2017 although I've made a few changes since then to support 20-digit InvoiceNo and a clearer error in the Job Log. The main point here is I've seen my own Perform out in the field (I recognized my coding convention) over a dozen times even though I didn't lay it down (kind of like my scripts). So IMHO, it's VERY possible they had Perform Logic for this in 2013. If you still have the old system go into Import Job Maint, pull up the import, and click on Perform then click the Lookup button. It may still be there but needs to point to a new folder.

https://90minds-com.socialcast.com/messages/5664955

Here is the one that Alnoor was referencing @DavidOverholt https://90minds-com.socialcast.com/messages/10804012

Thanks everyone! that did the trick of course!