Thanks
@Alnoor Cassim - The UDT table has two fields. The index (company code) and company name so it appears to meet the requirements. I want the company code to be uppercase when I add a line, but lower case is allowed currently. See clip. For my UDF's, the field is required to be uppercase. So every time I enter tst in the UDF, TST is returned. Not being able to mandate uppercase in the UDT is inconsistent, but not surprising (for Sage).
The UDT is very old so perhaps that is the issue, so perhaps that is the issue now. I don't create new codes often enough to delete the table and start over. The concept of this UDT is to have a code for every client. When I process a transaction that relates to a client, I code the line for that client. The GL detail posting history record is populated with the company code. This then allows me to query the GL transaction detail for a QAD client profitability report. Very useful when comparing clients for year over year (or trends). And it eliminates the need for a separate GL account client segment.
------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------
Original Message:
Sent: 09-25-2020 02:21
From: Alnoor Cassim
Subject: System UDT's v2020
Upper-case is forced on the UDT key if at the time of creation you add the key field plus one more (at least 2 fields).
See here - Sage City - UDF validation changes UDT value from lower case to upper case
So until fixed, workaround is to delete your UDT, recreate it with at least 2 fields.
------------------------------
Alnoor Cassim
Email: alnoor@asifocus.com
Ph: 949-689-9887
Orange County, CA
------------------------------