Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Restore found set after performing another Find

Featured Replies

Howdy, howdy:

I use the "TOG" method to save a found set (https://community.claris.com/en/s/question/0D73w000006YjbYCAS/detail ) , but I must be missing something: If no records are found, and I perform the Restore part of the script, the original found set isn't restored. How do I restore the original found set after a failed Find?

As an aside, I read elsewhere about creating a Summary field (List of record IDs) to create a list of primary keys to use later to restore a found set, but I don't know how to make use of it to restore a found set. How to?

As always, TIA for your help!

Rich 

Edited by Rich S
Minor correction

1 hour ago, Rich S said:

If no records are found, and I perform the Restore part of the script, the original found set isn't restored.

I am not able to reproduce this behavior.

 

1 hour ago, Rich S said:

I read elsewhere about creating a Summary field (List of record IDs) to create a list of primary keys to use later to restore a found set, but I don't know how to make use of it to restore a found set. How to?

If you put the list in a global field, you can then use a relationship matching the global to the primary key to go to related records.

 

I am not sure what exactly you are doing (and why), but perhaps you could simply open a new window before performing a new find? Then you will be able to return to the previous found set just by closing the new window.

 

Edited by comment

  • Author

A new window. Capital idea! I'll give that a shot in the morning. I'll also give the Summary field/Global field a try as well--it's good just to learn how things work, especially in a pinch.

  • 4 months later...
On 12/5/2023 at 12:15 AM, Rich S said:

A new window. Capital idea! I'll give that a shot in the morning. I'll also give the Summary field/Global field a try as well

Or ....use both, since the ExecuteSQL does not know of found sets, you often gather a list of ID's in a $$ variable, and loop thru each ID building native request upon request and make a final perform find. Using a new window and issue say a selfjoin GTRR(FS) in it, and then stuffing list of summaries into a $$ could mimic this approach ... by remembering to close the extra window just in time.

--sd

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.