FYI - In case you have BOI script that creates new sales orders:
Last night I troubleshot a 2020.1 Premium system running Operations Mgmt / JobOps. They had a BOI script that created new sales orders successfully during the v2020 test upgrade. They came from v2016. It was failing now that they were live. Something changed and I don't have the history but short of it is after script got the next new SO number it ran the normal nSetKey(SONumber) function but unexpectedly always returned an "
edit state" of 1 (existing order) instead of 2 (new order). This prevent the script from creating new orders.
Narrowed it down to SO_158SalesOrder_bus.pvc which was overriding the normal SetKey function. That in itself is not unusual as there as many places in regular Sage code that do that (e.g. IM_ItemCost_bus has it to prevent you from V/I importing new records into IM_ItemCost and only allowing you to update existing records).
Anyway, Scanco responded this morning to the reseller I helped acknowledging the issue and saying they will schedule it for fixing. I'll report back a date when I get one.
------------------------------
Alnoor Cassim
Email:
alnoor@asifocus.comPh:
Orange County, CA
------------------------------