7/4/2025 8:33:36 PM
|
|
slxdeveloper.com Community Forums |
|
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss general administration topics for SalesLogix (including LAN & remote topics). View the code of conduct for posting guidelines.
|
|
|
|
Picklist anomoly
Posted: 05 Sep 06 9:53 AM
|
fiogf49gjkf0d I have several county picklists in a client's slx system. On some screens the picklists perform fine. The picklist is set up as so: Required Entry checked, Text Must match a list item checked, Sorted Alpha checked, User cannot edit items checked.
When a user attempts to type something into the picklist control that does indeed match the picklist, they get a prompt saying their item must match the picklist. If you try several times it will eventually take the entry. Not a showstopper, but annoying for the client. Has anyone seen this before? Is there anything at the control level the sets picklist requirements?
They are running SLX 6.2 sp3 Thanks. |
|
|
|
Re: Picklist anomoly
Posted: 05 Sep 06 10:30 AM
|
fiogf49gjkf0d Hehe. That one is actually kind of funny. I have not seen that one before, but can't say I've ever tried either. Can you reproduce it on another system? |
|
|
|
Re: Picklist anomoly
Posted: 06 Sep 06 9:30 PM
|
fiogf49gjkf0d Originally posted by Steve Knowles
I have several county picklists in a client's slx system. On some screens the picklists perform fine. The picklist is set up as so: Required Entry checked, Text Must match a list item checked, Sorted Alpha checked, User cannot edit items checked. |
|
Just throwing this out there: Is it possible the users have their own values for the picklist? If "users cannot edit items" wasn't ALWAYS checked, it's possible that at some point they could have their own values and it's also possible that this conflicts with the "real" picklist.
I've personally never seen this but it's not a bad idea to double check your picklists via SQL queries and maybe even use the SLXProfiler.exe to make sure no weird SQL is being returned. If this is a data issue, you should be able to login from any machine as the user having the problem and be able to duplicate it.
The only other thing I can think of is having a code loop that updates a picklist with a value that isn't in the list but the control itself keeps the value the user selected. You can most likely trigger this by using an OnChange event to re-populate the picklist value. If a user selects a value, OnChange will fire and if you have code in the event that sets Picklist.Text to ANYTHING, OnChange will fire AGAIN. Theoretically you could send the control into an infinite loop this way but what may be happening is it gets to a point where it just gives up. It'd be pretty trivial to test this out too, just setup an OnChange event to set picklist.text equal to anything that isn't in the list then watch what happens when you try to select something. If you see the same behavior, most likely this is the culprit. |
|
|
|
Re: Picklist anomoly
Posted: 11 Sep 06 10:21 AM
|
fiogf49gjkf0d Actually a programming glitch.. The picklist in question is actually a county picklist dependant on which state is chosen. I was configuring the picklist on the 'On Popup' event. So when the user typed in the value without activiting the pickist, it threw the error because the proper picklist was never assigned to the control. When I returned to the issue for another look today it was crystal clear.
Thanks for the input. |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|