@Karen O'Lane - Nope you are 100% on base. Sage does mask the number in maintenance. I looked in the role maintenance and I could not find any role similar to PR setting allowing viewing, printing and editing of PII. Ugh.
@Michelle Taylor - I wonder if the listing RPT needs to be modified to include this table.
@Kevin Moyes - Interesting thought but I don't think it is workable for this opportunity. Access DB is menu driven. Client simply fires it up, data from all companies is pulled into the db via PTQ's, combined with union queries, select queries pull the bank required information which is outputted to a fixed length text file for uploading to bank. Entire process takes about a minute. I don't want to add steps to the process. Client hates change.
@Dan Burleson - Your solution for PR PII exports was genius. Will be contacting you. Hopefully, you can capture lightning in a bottle once again.
------------------------------
Jeff Schwenk
FORMER 90M Board Member -140,000,000 is a TERRIBLE thing to waste!!!
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------
Original Message:
Sent: 10-23-2021 03:00
From: Dan Burleson
Subject: v2021 - Exporting Bank Account Numbers, PII issues masking the Number
You could capture a preview session of the A/P Bank Code Listing Work table for each company and replace the base file (CI_BankCodeListingWrk) then link it to GL_Bank. They could change bank accounts so you could have me refresh this automatically if/when they do. At least this way you can point to the Bank Code Listing report as the Sage code that's exposing the sensitive information - not a UDF.
v2021

------------------------------
Dan Burleson
Software Consultant
Connex Software
Corvallis OR
541-224-6642
------------------------------
Original Message:
Sent: 10-22-2021 15:43
From: Kevin Moyes
Subject: v2021 - Exporting Bank Account Numbers, PII issues masking the Number
Do it as a custom report from within Sage, then export from there (instead of using ODBC).
We're going to run into the same problem with our Canadian EFT script (that uses ODBC)... and if you really don't care about PII security, you could add UDF's instead to GL_Bank... but you didn't get that idea from me. ;-)
------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
Original Message:
Sent: 10-22-2021 15:21
From: Michelle Taylor
Subject: v2021 - Exporting Bank Account Numbers, PII issues masking the Number
The PII worktable is in GL, as is the detail in GL_Bank. However, I don't think the table will allow the data be exported :(
------------------------------
Michelle Taylor
ERP Consulting Manager, CS3 Technology
918-388-9772
Original Message:
Sent: 10-22-2021 15:08
From: Karen O'Lane
Subject: v2021 - Exporting Bank Account Numbers, PII issues masking the Number
Hi, Jeff. I could be off base here, but have you checked Bank Code Maintenance to make sure that the bank account number field isn't actually masked there?
------------------------------
Karen O'Lane
Accounting Systems, Inc. (ASI)
Fresno CA
803.252.6154 x242
559.577.4142
90 Minds Treasurer