The Omit Record script step toggles the Omit option in Find mode.
I think these are the script steps you want
Enter find mode
set field(actions deadline::date...
set field status = finished
While the other posters are correct, after all these years I still find it VERY confusing for people stepping in Filemaker's scripting world and wording to use the "Omit Record" script step for achieving what the OP wants.
The correct script step, ensuring that the reader of our script understands what's going on (and that includes ourselves after 3 years of not looking at the script) would be
New find Request [type = add, omit, constrain, extend]
maybe in Filemaker 17 ?
thanks everyone. I wasn't sure weather it was omit record or omit multiple records. works great now
yes, good answers! I also want to point out that Restore is probably not to be done in scripted finds, as you may 'undo' what you previously scripted. Just Perform Find (no options) is preferred - be aware of how this works!
I like to do this:
Enter Find Mode (no restore, no pause)
... do your find criteria ...
Perform Find (no restore)
OR use Enter Find Mode ( restore ) instead of above
OR use Perform Find ( restore ) instead of above
From there you can:
Modify Last Find
Constrain Found Set (for scripted, probably no restore)
Extend Found Set (for scripted, probably no restore)
Generally I try to figure out what to do manually and then script from there. I also like to think of the GTRR (Go to Related Records) as a find from parent to child records and may use it like the "restore" and perhaps use the Constrain or Extend from there.
I opine that the full steps for scripted finds are easier to debug then having to peek at what's 'stored' in the Enter Find Mode (restore), Perform Find (restore), Constrain Found Set (restore), or Extend Found Set (restore).
completely agree. Restore sux 101% on the script readability scale, too.