Sage 100

@Jeff Schwenk asked me recently if the Perform Logic I shared several years ago for preventing duplicate invoices from A/P Invoice imports could be re-purposed for A/P Manual Check Entry​. In both cases by default, V/I treats an existing Invoice No on an import as an Adjustment instead of a duplicate to reject.

So here is one I did for a client last year for A/P Manual Check Entry.
Slightly different than the one A/P Invoice Data Entry.
This worked for Jeff for 2019 Adv and 2018 Adv.
Happy importing!

In Import Job Maintenance click on Perform button and set it up like this:


Create a folder called PFM under \Mas90 and place the attached Import_ManChk_ValidateInvoiceNo.txt there. 
Note: You don't have to put it in PFM folder. That is just my own convention.
When a dupe is found it will force the record to fail and it will appear in the Job Log.

------------------------------
Alnoor Cassim

Free Agent Developer and Consultant
CallForHelp.biz
Email: alnoor@callforhelp.biz
Orange County, CA
------------------------------

(I'm in the habit of setting up PL files in CM\Script, so I don't have to remember to copy them during migrations / upgrades... that folder is copied automatically, and all kinds of scripts are in one place).

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

I'm with @Kevin Moyes on placing any customization related files in CM\Script​.

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------

Original Message:
Sent: 05-13-2019 09:26
From: Kevin Moyes
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

(I'm in the habit of setting up PL files in CM\Script, so I don't have to remember to copy them during migrations / upgrades... that folder is copied automatically, and all kinds of scripts are in one place).

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

That seems like a good practice. For me most of my customizations are actually mods where the Script folder is not in play so I'm accustomed already to a reinstallation process as part of an upgrade. It works for me.

------------------------------
Alnoor Cassim

Free Agent Developer and Consultant
CallForHelp.biz
Email: alnoor@callforhelp.biz
Orange County, CA
------------------------------

Original Message:
Sent: 05-14-2019 11:46
From: David Speck II
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

I'm with @Kevin Moyes on placing any customization related files in CM\Script​.

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------


Original Message:
Sent: 05-13-2019 09:26
From: Kevin Moyes
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

(I'm in the habit of setting up PL files in CM\Script, so I don't have to remember to copy them during migrations / upgrades... that folder is copied automatically, and all kinds of scripts are in one place).

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

I tried this one for my manual check VI job, using the same text file and perform logic but it is not working @Alnoor Cassim. ​I created a PFM folder under MAS90 but does the Command simply start with ..\PFM\.... or do I have to have the full path to the MAS90 directory? This is v2018 standard, BTW.

------------------------------
Therese Logeais, Technology Integrators
------------------------------

Original Message:
Sent: 05-14-2019 12:02
From: Alnoor Cassim
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

That seems like a good practice. For me most of my customizations are actually mods where the Script folder is not in play so I'm accustomed already to a reinstallation process as part of an upgrade. It works for me.

------------------------------
Alnoor Cassim

Free Agent Developer and Consultant
CallForHelp.biz
Email: alnoor@callforhelp.biz
Orange County, CA
------------------------------


Original Message:
Sent: 05-14-2019 11:46
From: David Speck II
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

I'm with @Kevin Moyes on placing any customization related files in CM\Script​.

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 05-13-2019 09:26
From: Kevin Moyes
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

(I'm in the habit of setting up PL files in CM\Script, so I don't have to remember to copy them during migrations / upgrades... that folder is copied automatically, and all kinds of scripts are in one place).

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

..\PFM\[Script Name] should work. I have gotten in the habit of using relative path names for my scripts and perform logic, makes upgrades and server moves much easier.

Double check the extension of the actual file and the extension you are specifying in the path.

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------

Original Message:
Sent: 01-02-2020 16:27
From: Therese Logeais
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

I tried this one for my manual check VI job, using the same text file and perform logic but it is not working @Alnoor Cassim. ​I created a PFM folder under MAS90 but does the Command simply start with ..\PFM\.... or do I have to have the full path to the MAS90 directory? This is v2018 standard, BTW.

------------------------------
Therese Logeais, Technology Integrators
------------------------------


Original Message:
Sent: 05-14-2019 12:02
From: Alnoor Cassim
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

That seems like a good practice. For me most of my customizations are actually mods where the Script folder is not in play so I'm accustomed already to a reinstallation process as part of an upgrade. It works for me.

------------------------------
Alnoor Cassim

Free Agent Developer and Consultant
CallForHelp.biz
Email: alnoor@callforhelp.biz
Orange County, CA


Original Message:
Sent: 05-14-2019 11:46
From: David Speck II
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

I'm with @Kevin Moyes on placing any customization related files in CM\Script​.

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 05-13-2019 09:26
From: Kevin Moyes
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

(I'm in the habit of setting up PL files in CM\Script, so I don't have to remember to copy them during migrations / upgrades... that folder is copied automatically, and all kinds of scripts are in one place).

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

It's a .txt file and that is what is specified in the command line.

------------------------------
Therese Logeais, Technology Integrators
------------------------------

Original Message:
Sent: 01-02-2020 16:48
From: David Speck II
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

..\PFM\[Script Name] should work. I have gotten in the habit of using relative path names for my scripts and perform logic, makes upgrades and server moves much easier.

Double check the extension of the actual file and the extension you are specifying in the path.

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------


Original Message:
Sent: 01-02-2020 16:27
From: Therese Logeais
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

I tried this one for my manual check VI job, using the same text file and perform logic but it is not working @Alnoor Cassim. ​I created a PFM folder under MAS90 but does the Command simply start with ..\PFM\.... or do I have to have the full path to the MAS90 directory? This is v2018 standard, BTW.

------------------------------
Therese Logeais, Technology Integrators


Original Message:
Sent: 05-14-2019 12:02
From: Alnoor Cassim
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

That seems like a good practice. For me most of my customizations are actually mods where the Script folder is not in play so I'm accustomed already to a reinstallation process as part of an upgrade. It works for me.

------------------------------
Alnoor Cassim

Free Agent Developer and Consultant
CallForHelp.biz
Email: alnoor@callforhelp.biz
Orange County, CA


Original Message:
Sent: 05-14-2019 11:46
From: David Speck II
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

I'm with @Kevin Moyes on placing any customization related files in CM\Script​.

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 05-13-2019 09:26
From: Kevin Moyes
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

(I'm in the habit of setting up PL files in CM\Script, so I don't have to remember to copy them during migrations / upgrades... that folder is copied automatically, and all kinds of scripts are in one place).

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

Do you get any error messages?

Can you include a screenshots of the file name in the PFM folder and the perform logic set up dialogue?

Any chance NTFS permissions aren't set correctly on the PFM folder?

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------

Original Message:
Sent: 01-02-2020 17:01
From: Therese Logeais
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

It's a .txt file and that is what is specified in the command line.

------------------------------
Therese Logeais, Technology Integrators
------------------------------


Original Message:
Sent: 01-02-2020 16:48
From: David Speck II
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

..\PFM\[Script Name] should work. I have gotten in the habit of using relative path names for my scripts and perform logic, makes upgrades and server moves much easier.

Double check the extension of the actual file and the extension you are specifying in the path.

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 01-02-2020 16:27
From: Therese Logeais
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

I tried this one for my manual check VI job, using the same text file and perform logic but it is not working @Alnoor Cassim. ​I created a PFM folder under MAS90 but does the Command simply start with ..\PFM\.... or do I have to have the full path to the MAS90 directory? This is v2018 standard, BTW.

------------------------------
Therese Logeais, Technology Integrators


Original Message:
Sent: 05-14-2019 12:02
From: Alnoor Cassim
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

That seems like a good practice. For me most of my customizations are actually mods where the Script folder is not in play so I'm accustomed already to a reinstallation process as part of an upgrade. It works for me.

------------------------------
Alnoor Cassim

Free Agent Developer and Consultant
CallForHelp.biz
Email: alnoor@callforhelp.biz
Orange County, CA


Original Message:
Sent: 05-14-2019 11:46
From: David Speck II
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

I'm with @Kevin Moyes on placing any customization related files in CM\Script​.

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 05-13-2019 09:26
From: Kevin Moyes
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

(I'm in the habit of setting up PL files in CM\Script, so I don't have to remember to copy them during migrations / upgrades... that folder is copied automatically, and all kinds of scripts are in one place).

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

FYI - I remoted in with Therese to see what was going on. It turns out my "prefix" variables for APDivisionNo$ and VendorNo$ were out of scope and that's why it was always returning the InvoiceNo as not found (therefore not a duplicate) when running the CheckInvoiceHistory() method. For @Jeff Schwenk who I did this for originally, these variables were in scope. I presume the difference is in the Sage version. Therese's customer was on 2018 PU2, Jeff's was earlier I think.

Anyway the right way to fix is add Perform Logic at an earlier point when the variables are in scope, assign them to a global variable, then use them in this main Perform. Instead I directly "replaced" VendorNo from the import file column. Putting it together this line is changed:

retExists = coInvcHistHdr'CheckInvoiceHistory("00", IMP$[2], InvoiceNo$)

The "00" means no divisions were used. The [2] refers to VendorNo being Column 2 in the source import file. This worked for Therese.

------------------------------
Alnoor Cassim

Accounting Systems, Inc. (ASI)
Email: alnoor@asifocus.com
Orange County, CA
------------------------------

Original Message:
Sent: 01-02-2020 17:25
From: David Speck II
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

Do you get any error messages?

Can you include a screenshots of the file name in the PFM folder and the perform logic set up dialogue?

Any chance NTFS permissions aren't set correctly on the PFM folder?

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------


Original Message:
Sent: 01-02-2020 17:01
From: Therese Logeais
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

It's a .txt file and that is what is specified in the command line.

------------------------------
Therese Logeais, Technology Integrators


Original Message:
Sent: 01-02-2020 16:48
From: David Speck II
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

..\PFM\[Script Name] should work. I have gotten in the habit of using relative path names for my scripts and perform logic, makes upgrades and server moves much easier.

Double check the extension of the actual file and the extension you are specifying in the path.

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 01-02-2020 16:27
From: Therese Logeais
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

I tried this one for my manual check VI job, using the same text file and perform logic but it is not working @Alnoor Cassim. ​I created a PFM folder under MAS90 but does the Command simply start with ..\PFM\.... or do I have to have the full path to the MAS90 directory? This is v2018 standard, BTW.

------------------------------
Therese Logeais, Technology Integrators


Original Message:
Sent: 05-14-2019 12:02
From: Alnoor Cassim
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

That seems like a good practice. For me most of my customizations are actually mods where the Script folder is not in play so I'm accustomed already to a reinstallation process as part of an upgrade. It works for me.

------------------------------
Alnoor Cassim

Free Agent Developer and Consultant
CallForHelp.biz
Email: alnoor@callforhelp.biz
Orange County, CA


Original Message:
Sent: 05-14-2019 11:46
From: David Speck II
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

I'm with @Kevin Moyes on placing any customization related files in CM\Script​.

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 05-13-2019 09:26
From: Kevin Moyes
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

(I'm in the habit of setting up PL files in CM\Script, so I don't have to remember to copy them during migrations / upgrades... that folder is copied automatically, and all kinds of scripts are in one place).

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

Thanks again, @Alnoor Cassim!!​

------------------------------
Therese Logeais, Technology Integrators
------------------------------

Original Message:
Sent: 01-03-2020 15:39
From: Alnoor Cassim
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

FYI - I remoted in with Therese to see what was going on. It turns out my "prefix" variables for APDivisionNo$ and VendorNo$ were out of scope and that's why it was always returning the InvoiceNo as not found (therefore not a duplicate) when running the CheckInvoiceHistory() method. For @Jeff Schwenk who I did this for originally, these variables were in scope. I presume the difference is in the Sage version. Therese's customer was on 2018 PU2, Jeff's was earlier I think.

Anyway the right way to fix is add Perform Logic at an earlier point when the variables are in scope, assign them to a global variable, then use them in this main Perform. Instead of that, I manually assigned the VendorNo from the import file column directly. Putting it together the retExists line changes to:

retExists = coInvcHistHdr'CheckInvoiceHistory("00", IMP$[2], InvoiceNo$)

In this case "00" means no divisions were used. Also the [2] was the VendorNo column. This worked for Therese.

------------------------------
Alnoor Cassim

Accounting Systems, Inc. (ASI)
Email: alnoor@asifocus.com
Orange County, CA
------------------------------


Original Message:
Sent: 01-02-2020 17:25
From: David Speck II
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

Do you get any error messages?

Can you include a screenshots of the file name in the PFM folder and the perform logic set up dialogue?

Any chance NTFS permissions aren't set correctly on the PFM folder?

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 01-02-2020 17:01
From: Therese Logeais
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

It's a .txt file and that is what is specified in the command line.

------------------------------
Therese Logeais, Technology Integrators


Original Message:
Sent: 01-02-2020 16:48
From: David Speck II
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

..\PFM\[Script Name] should work. I have gotten in the habit of using relative path names for my scripts and perform logic, makes upgrades and server moves much easier.

Double check the extension of the actual file and the extension you are specifying in the path.

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 01-02-2020 16:27
From: Therese Logeais
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

I tried this one for my manual check VI job, using the same text file and perform logic but it is not working @Alnoor Cassim. ​I created a PFM folder under MAS90 but does the Command simply start with ..\PFM\.... or do I have to have the full path to the MAS90 directory? This is v2018 standard, BTW.

------------------------------
Therese Logeais, Technology Integrators


Original Message:
Sent: 05-14-2019 12:02
From: Alnoor Cassim
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

That seems like a good practice. For me most of my customizations are actually mods where the Script folder is not in play so I'm accustomed already to a reinstallation process as part of an upgrade. It works for me.

------------------------------
Alnoor Cassim

Free Agent Developer and Consultant
CallForHelp.biz
Email: alnoor@callforhelp.biz
Orange County, CA


Original Message:
Sent: 05-14-2019 11:46
From: David Speck II
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

I'm with @Kevin Moyes on placing any customization related files in CM\Script​.

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 05-13-2019 09:26
From: Kevin Moyes
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

(I'm in the habit of setting up PL files in CM\Script, so I don't have to remember to copy them during migrations / upgrades... that folder is copied automatically, and all kinds of scripts are in one place).

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

Hmmm, moved client to v2020 a couple months back.  They haven't reported any issues but a good reseller would verify.

------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------

Original Message:
Sent: 01-03-2020 16:03
From: Therese Logeais
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

Thanks again, @Alnoor Cassim!!​

------------------------------
Therese Logeais, Technology Integrators
------------------------------


Original Message:
Sent: 01-03-2020 15:39
From: Alnoor Cassim
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

FYI - I remoted in with Therese to see what was going on. It turns out my "prefix" variables for APDivisionNo$ and VendorNo$ were out of scope and that's why it was always returning the InvoiceNo as not found (therefore not a duplicate) when running the CheckInvoiceHistory() method. For @Jeff Schwenk who I did this for originally, these variables were in scope. I presume the difference is in the Sage version. Therese's customer was on 2018 PU2, Jeff's was earlier I think.

Anyway the right way to fix is add Perform Logic at an earlier point when the variables are in scope, assign them to a global variable, then use them in this main Perform. Instead of that, I manually assigned the VendorNo from the import file column directly. Putting it together the retExists line changes to:

retExists = coInvcHistHdr'CheckInvoiceHistory("00", IMP$[2], InvoiceNo$)

In this case "00" means no divisions were used. Also the [2] was the VendorNo column. This worked for Therese.

------------------------------
Alnoor Cassim

Accounting Systems, Inc. (ASI)
Email: alnoor@asifocus.com
Orange County, CA


Original Message:
Sent: 01-02-2020 17:25
From: David Speck II
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

Do you get any error messages?

Can you include a screenshots of the file name in the PFM folder and the perform logic set up dialogue?

Any chance NTFS permissions aren't set correctly on the PFM folder?

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 01-02-2020 17:01
From: Therese Logeais
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

It's a .txt file and that is what is specified in the command line.

------------------------------
Therese Logeais, Technology Integrators


Original Message:
Sent: 01-02-2020 16:48
From: David Speck II
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

..\PFM\[Script Name] should work. I have gotten in the habit of using relative path names for my scripts and perform logic, makes upgrades and server moves much easier.

Double check the extension of the actual file and the extension you are specifying in the path.

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 01-02-2020 16:27
From: Therese Logeais
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

I tried this one for my manual check VI job, using the same text file and perform logic but it is not working @Alnoor Cassim. ​I created a PFM folder under MAS90 but does the Command simply start with ..\PFM\.... or do I have to have the full path to the MAS90 directory? This is v2018 standard, BTW.

------------------------------
Therese Logeais, Technology Integrators


Original Message:
Sent: 05-14-2019 12:02
From: Alnoor Cassim
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

That seems like a good practice. For me most of my customizations are actually mods where the Script folder is not in play so I'm accustomed already to a reinstallation process as part of an upgrade. It works for me.

------------------------------
Alnoor Cassim

Free Agent Developer and Consultant
CallForHelp.biz
Email: alnoor@callforhelp.biz
Orange County, CA


Original Message:
Sent: 05-14-2019 11:46
From: David Speck II
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

I'm with @Kevin Moyes on placing any customization related files in CM\Script​.

------------------------------
David Speck II
Tennessee Software Solutions


Original Message:
Sent: 05-13-2019 09:26
From: Kevin Moyes
Subject: Perform Logic to Prevent Duplicate Invoice on A/P Manual Check Entry

(I'm in the habit of setting up PL files in CM\Script, so I don't have to remember to copy them during migrations / upgrades... that folder is copied automatically, and all kinds of scripts are in one place).

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