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.

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.

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!