Glad it worked out! Let me mention a few things:
1. Normally when you install a Product Update that changes the dictionary (such as adding a new field to a table), it requires you to click Convert in Company Maint where you can select all companies. This updates all the physical tables for you. I don't know why that didn't happen here.
2. I could write a proper utility to run Update_Physical function for all companies but here is an alternate way from SYZCON so you don't have to keep switching companies at the Launcher and changing the table name on command line. On Below for SYZCON use the up arrow key on your keyboard to repeat last command so you can quickly change the module and company code and press Enter again. It's a bit tricky at first but you'll get the hang of it.
E.g. if companies to "update physical" are ABC,MFG, and XYZ then from SYZCON:
(The Activate function below does Update_Physical for all tables based on module and company code)
(Anything after ! symbol is just a comment, NOT something you need to type)
oAct = NEW("Sy_Activation_bus", %SYS_SS)
print oAct'Activate("A/R", "ABC") ! If it returns 1 then hooray. If not type PRINT oAct'LastErrorMsg$
print oAct'Activate("S/O", "ABC") ! Use the up arrow key to recall last command. Change the A/R to S/O and press Enter
print oAct'Activate("A/R", "MFG") ! Use the up arrow key to recall last command. Change S/O to A/R and ABC to MFG
print oAct'Activate("S/O", "MFG") ! Use the up arrow key to recall last command. Change the A/R to S/O
print oAct'Activate("A/R", "XYZ") ! Use the up arrow key to recall last command. Change S/O to A/R and MFG to XYZ
print oAct'Activate("S/O", "XYZ") ! Use the up arrow key to recall last command. Change A/R to S/O
Type BYE to exit.
------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)
Email:
alnoor@asifocus.comOrange County, CA
------------------------------
Original Message:
Sent: 07-01-2020 21:05
From: Susan Pawlowic
Subject: eInvoice Payments Error
I learned a few things:
1 - Alnoor's utility must be run for each live company. Log in as first live company; run; log in as second live company; run; etc.
2 - After running the utilty for AR_Customer, you can then perform a VI import to populate the AR_Customer eInvoice Payments field with N.
3 - The other two tables this needs to be run for are AR_InvoiceHeader and SO_InvoiceHeader, as applicable to the company(s).
Thanks again, this saved the day for the client!
------------------------------
Susan Pawlowic
consultant
RKL eSolutions, LLC
------------------------------
Original Message:
Sent: 07-01-2020 15:29
From: Susan Pawlowic
Subject: eInvoice Payments Error
I didn't either. Thanks, I'll try that tonight when users are all out. Will let you know if it works!
------------------------------
Susan Pawlowic
consultant
RKL eSolutions, LLC
Original Message:
Sent: 07-01-2020 15:02
From: Alnoor Cassim
Subject: eInvoice Payments Error
You know I didn't realize SO_InvoiceHeader has an EInvoicePayments field too. So after everything has calmed down, try the same steps but point it to SO_InvoiceHeader
------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)
Email: alnoor@asifocus.com
Orange County, CA
Original Message:
Sent: 07-01-2020 14:51
From: Susan Pawlowic
Subject: eInvoice Payments Error
Thank you, Alnoor. I ran this and received no errors. It reset the customer's value back to blank so I changed it again in DFDM. I am still getting the error when I try to create an invoice. I'm going to disable "write to invoice" in Starship so they can get their shipments out today, since it's almost 3 p.m. Then I will need to circle back to Sage.
I ran the above and received no errors, it did reset the one customer's field value back to blank so I changed it again in DFDM; and I am still getting the error when processing an invoice. Since it's almost 3 p.m., I'm going to disable 'write to invoice' in Starship so that they can get their shipments out, but I am going to have to go back to Sage for this.
------------------------------
Susan Pawlowic
consultant
RKL eSolutions, LLC
Original Message:
Sent: 07-01-2020 13:57
From: Alnoor Cassim
Subject: eInvoice Payments Error
"The column is not in the IO list" would seem to indicate although the eInvoice column is in the dictionary for AR_Customer (and clearly it's marked as a Required field), the physical table may not have been updated to reflect that. So first just try clicking on Convert in Company Maintenance. Otherwise here is something you can do from SYZCON to update the physical table. Everybody must out of screens that touch AR_Customer.
t$ = "AR_Customer"
CALL "*DICT/DD_UPDT;Update_Physical",t$,$$,$$,error$
print error$
If error$ is blank then that means no errors. You can type BYE to exit.
------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)
Email: alnoor@asifocus.com
Orange County, CA