![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hello, In find mode I've got a drop-down that allows users to input a group key. The drop-down shows the list of group names, but when the user makes her selection, it's the group key that displays in the field. That's is what I want to be in the input field as I need to search on the key. Now when users input a key in browse mode I am able to overlay the input field with the related group's name so that the user never gets to see the key field. This approach does not work in find mode. How can I have my cake and eat it? I want to have user input the key field but display the correct group name instead. Can you suggest a workaround? Many thanks Kevin |
)
#3
| |||
| |||
|
|
If there is already a "Group Name" Field (or you could add one), then you can just use that to perform the FInd. Say the user searches for "Agency" then it will come up with both of |
|
Another option is to Script the Find. Have the User enter the requested "Group Name" data into a Global Field and then use a Script 'convert' that into the "Group Key" data, put it into the appropriate Find Request Field and then process the Find. I've already got the scripting infrastructure in place for finds so |
#4
| |||
| |||
|
|
In find mode I've got a drop-down that allows users to input a group key. The drop-down shows the list of group names, but when the user makes her selection, it's the group key that displays in the field. That's is what I want to be in the input field as I need to search on the key. Now when users input a key in browse mode I am able to overlay the input field with the related group's name so that the user never gets to see the key field. This approach does not work in find mode. How can I have my cake and eat it? I want to have user input the key field but display the correct group name instead. Can you suggest a workaround? Many thanks Kevin |
#5
| |||
| |||
|
|
Kevin, Instead of a drop down list, you can use a pop up menu. *I |
#6
| |||
| |||
|
|
Thanks Harry for your quick reply. Here's my response to your suggestions: If there is already a "Group Name" Field (or you could add one), then you can just use that to perform the FInd. Say the user searches for "Agency" then it will come up with both of the following groups "Agency" and "Previous Agency". But now thinking aloud, I think your suggestion of pre-processing the find layout before allowing the find function to continue (see below) might work well here. I can concatenate the prefix "==" onto the group field. That will fix the problem of ambiguity. Another option is to Script the Find. Have the User enter the requested "Group Name" data into a Global Field and then use a Script 'convert' that into the "Group Key" data, put it into the appropriate Find Request Field and then process the Find. I've already got the scripting infrastructure in place for finds so that's not a problem. My hunch is that I won't be able to do the scripted lookup on the group name to find out the matching key while in find mode. The relationships won't evaluate in find mode. Does anyone else have any suggestions/comments? |
)
#7
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |