
06-05-2009 10:34 AM
Hi all.
We have a pick list whose attributes are the following:
1. Text must match a list item
2. Users cannot edit items
The other attributes are blank.
The problem we are having is that the first value in the picklist is <None> and some users are selecting that, and that is entering <NULL> in the table. We do not want to check the "Required Entry" checkbox because that forces the end user to select something, but there may be times when they accidentally enter the picklist. How can we avoid entering <NULL> without requiring entry?
SLX LAN v7.2.1
Thank you in advance!
Solved! Go to Solution.
06-05-2009 12:42 PM
06-05-2009 01:45 PM
06-05-2009 02:11 PM
Normally a field IS NULL is SalesLogix - until you actually put something in it.
The code should just prevent the user from continuing.. and have to choose something - or set a default.
You can do all that w/out code by just using the Picklist options. - What do you really want to save?
06-05-2009 02:13 PM
06-05-2009 02:18 PM
06-05-2009 02:38 PM
06-05-2009 03:11 PM
Forgive me if this is too "database 101" but if the field is not required to have a value, then <NULL> in the database means no value. If other fields in the record are being populated, then SLX will still save the record, but with no value - <NULL> in that field. In most cases, this does not present a problem in SalesLogix.
Exceptions would be numeric fields which are used in mathmatic formulas or text concantenation (you have a "select color" picklist and later refer to a Red Widget, using the selected color). To avoid type mismatches here you'd have to default these fields to 0 or a blank value (blank in a a text field IS a value), or use code to avoid using these fields when they are null.
06-08-2009 05:36 AM
Got it. Thanks!