Sounds like you might have to script it.  You should be able to find some examples of using oScript.SetError on a pre-validate event and how to read UDTs using the BOI.  I have an example on here on how to add a lookup to a field too, although I don't think I have ever tried it with a UDT but if an ALE record is created in the User Lookup Wizard for you UDT then you should be able to use it with my script example.

If you are not using the UDF in other company codes, set the validation in UDF maintenance (tab 2) and don't mark it as required.

I think the issue is that they are wanting to set the validation on the standard CustomerType field, not a UDF, although this brings up another way to handle this, create a UDF to hold the customer type but only add it to Customer Maintenance in Customizer for the target company.  Could then use a simple post validate script on the UDF to mirror the UDF value to the CustomerType field so it can be leveraged throughout Sage 100 where the CustomerType is used.

Good catch.  I didn't notice it was a Sage field (not a UDF).

I like the mirror script too... perhaps coupled with a company specific panel to show either the UDF or regular field.

David Speck  when the UDT is created there will be an associated Lookup created as well, that can be used for your example.  And the CM_UDT_svc object can be used to validate the entry.

oUDT = oSession.GetObject("CM_UDT_svc", "AR_UDT_CustomerType")

Set oUDT = oScript.AsObject(oUDT)

It can then be used like any other Service object using .Find etc.

E

Thanks for confirming that regarding the ALE lookup, I thought I recall seeing one in the User Lookup Wizard at one point but wasn't certain.

Thank you everyone. I'm not the best at scripting but will give it a try. We would like to use the standard customer type field rather than a udf so these suggestions are great! Much appreciated!