Sage 100

I'm in the midst of a small project to import sales orders into Sage 100 using Visual Integrator. The import works fine and the customer has it setup for unattended uploads.

The issue is that periodically the feed (CSV) into Sage has an invalid item. Either the item doesn't exist or it's Discontinued ( or whatever status prevents putting it onto a sales order).  This causes one or more lines to fail although the order may partially import ( except for the failed lines).

What are the options for error trapping for failed lines on an unattended VI job? I think ideally the customer would like to get an email alert about a failed upload. I've suggested they might create a UDF to hold the check total of what the customer expects the order to total to. Then I could use Visual Cut on the just imported orders to send an alert for any that imported for less than the full amount ( this doesn't solve for any that don't import at all ).

Are there other ways that you have tackled this and, if so, how? 

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
CT
------------------------------

------------------------------
Bill Pfahnl
Nims & Associates
------------------------------

I used to have the below success/failure routines for VI for a client back a couple decades.  Can't remember exactly why I couldn't continue using them for other clients.  Possibly because I didn't have someone to edit/create the .exe's?  And/or maybe something to do with the updated Perform Logic?

edit:  Actually yes I remember now, it's because the Success and Failure conditions were no longer available in VI.

------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area
------------------------------

Original Message:
Sent: 01-09-2025 14:24
From: Bill Pfahnl
Subject: Error reporting for unattended VI jobs

I've tackled a similar situation before: when an item doesn't exist, it gets marked as a special item by appending an asterisk (*) before the item code. This preserves the number, ensuring the order remains intact and can be edited or corrected later. This process uses temporary fields and conditional statements for both the item code and item type. Luckily, our file had a marker to distinguish stock items. It's possible someone here has, or can develop, perform logic to validate against inventory and achieve the same functionality.

------------------------------
Bill Pfahnl
Nims & Associates
------------------------------

Also don't forget about the VI Options, in case you can leverage that:

------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area
------------------------------

Original Message:
Sent: 01-09-2025 16:19
From: Brett Zimmerman
Subject: Error reporting for unattended VI jobs

I used to have the below success/failure routines for VI for a client back a couple decades.  Can't remember exactly why I couldn't continue using them for other clients.  Possibly because I didn't have someone to edit/create the .exe's?  And/or maybe something to do with the updated Perform Logic?

------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area
------------------------------


Original Message:
Sent: 01-09-2025 14:24
From: Bill Pfahnl
Subject: Error reporting for unattended VI jobs

I've tackled a similar situation before: when an item doesn't exist, it gets marked as a special item by appending an asterisk (*) before the item code. This preserves the number, ensuring the order remains intact and can be edited or corrected later. This process uses temporary fields and conditional statements for both the item code and item type. Luckily, our file had a marker to distinguish stock items. It's possible someone here has, or can develop, perform logic to validate against inventory and achieve the same functionality.

------------------------------
Bill Pfahnl
Nims & Associates

dup

We've usually just set up an automated email against the SY_ActivityLog record(s) pertaining to the job.  Someone just needs to look quickly to see if there was a failure.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------