Classification: UNCLASSIFIED Caveats: NONE
Related topic with the Drop-Down List: On the Summary+ field on the Requester Console, we have the Summary menu set as some have recommended here: drop-down list with a menu. The query works correctly if I make the menu editable, but it doesn't force the selection from the existing menu if the user escapes out of the drop-down list. The goal is either drop-down list OR query using Full Text search (but not a new entry) However, we want to be able to allow free form text to find matches using Full Text Search against the summary list, but not allow free form text to be entered. Has anyone done this before? I'm sure there's a simple way to address it. Thanks in advance. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Bean Sent: Thursday, March 06, 2008 2:15 PM To: [email protected] Subject: Re: Pattern of $MENU$ ** $MENU$ patterns below version will work in earlier versions of ARS, but not if the search qualification defined in the search menu contains a dynamic field reference. e.g.: 'Equipment Category' = $536870913$ There was a workaround for this, however (see attached). This workaround should still be valid on later versions of ARS. However, it would be MUCH simpler to follow Joe's suggestion, and change the display type to 'Drop-Down List' in the display properties of the character field to which the search menu is attached (unless for some reason you don't want the character field to look like a selection field). HTH, --Thomas ----- Original Message ----- From: Joe D'Souza <mailto:[EMAIL PROTECTED]> Newsgroups: gmane.comp.crm.arsystem.general To: [email protected] Sent: Wednesday, March 05, 2008 9:17 PM Subject: Re: Pattern of $MENU$ ** Andy, If you hare having the field patterned using $MENU$, why do you type into it or let your users type into it? Can't you just have the character field displayed as a drop-list and have the users forced to use the menus? That's an available feature in ARS version 6.3 upwards.. That would be clean and you would get what you want to do... If you are below version 6, and somewhere close to version 4.5, there used to be a bug with the $MENU$ patterning.. Even valid values would be rejected. The only fix on that version was to upgrade it. I do not recall a patch that fixed it except the next upgrade.. Cheers Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected] <mailto:[email protected]> ]On Behalf Of Mayfield, Andy L. Sent: Wednesday, March 05, 2008 6:35 PM To: [email protected] Subject: Pattern of $MENU$ I'm sure there is a simple answer for this, but I am encountering an error when attempting to write a value to a new character field. The error I get is "ARERR [306] Value does not fall within the limits specified for the field : (MENU - $MENU$) : Equipment Type" when trying to write to the field. On the field properties - attributes tab, I have Pattern set to $MENU$ and I have a menu that pull available values from another form created to hold the available options. The drop-down menu lists the appropriate options, but when I select one of them and try to save I get the error listed above. My understanding was that the $MENU$ option was to make sure that you selected a value from the menu, so I am confused as to what the problem might be. Thanks in advance for any help you can give. Andy L. Mayfield Sr. System Operation Specialist Alabama Power Company Office: 205-226-1805 Cell: 205-288-9140 SoLinc: 10*19140 __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ Classification: UNCLASSIFIED Caveats: NONE _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
