1.the use of global fields in a scripted find?
2. conditional sorts in a portal?
3. Resorting a summary list when the data is resorted?
Can you explain a little more about #1, do you want to search on the content of a global field? That wouldn't make sense because all fields share the same content for those fields.
On the other hand, using data entered into a global field to set up and perform finds is a routine thing done in many solutions.
See: Scripted Find Examples
And dynamically sorting the contents of a portal IS possible, though it's a work around for something many would like to do without the work around.
Resorting a summary list when the data is resorted?
Can you provide an example of what you mean by that and how you'd find it useful?
#1 I'm referring to the perform find script step where you select the field to match and the matching criteria. It would be helpful to be able to enter a global on the criteria side. I use the method outlined in the scripted find but i prefer to use the stored find. You should be able to do it both ways.
#2 it is often required to display portal results in different ways. To be able to change the sort order based on user selection would be benefiical. At present you have to overlay copies of the portal and hide depending on the selection.
#3 relates to the portal sort. I have a portal fed by a summary list of primary keys from a found list. if I resort the found list the summary list is not resorted. I thought that this could have resolved the portal sort issue that i was having.
Thanks for the comments
1) that's very different from your original post. Personally, I never used stored find criteria. Not only for the limitation here, but because I don't care to have to drill down into additional dialogs just to see what find criteria is being set up for the find.
2) can be done now, though improvements to the product could make this easier to do than it is now. You do not have to overlay copies of the portal though doing so is one option.
3) Since you can dynamically sort a portal now, I don't see much advantage to 3)
If you search for threads on sorting portals, there's an option that uses a calculation field to extract and format different data from other fields in the portal based on which sort field is selected. You then always sort on the calculation field but since the field copies data from different fields based on the sort option selected, you get the dynamic sorting you describe here.
philmodjunk wrote: 1) that's very different from your original post. Personally, I never used stored find criteria. Not only for the limitation here, but because I don't care to have to drill down into additional dialogs just to see what find criteria is being set up for the find.
Ditto. We highly discourage our developers from using stored finds. The UI for it is confusing and it makes the code not readable.
#1 OK accepted
#2&3 Thanks for the pointer I'll try and find the thread and investigate further.
Retrieving data ...