What you want to do is
1. go into find mode
2. enter 1234
3. create new record request
4. enter 5678
5. perform find
this will create an OR search that will return records with 1234 Or 5678 in the field
This is exactly what I am NOT trying to do for 100 serial numbers. Is there no simple way to just do something in my "Serial Number" field like
1234 OR 4567 OR 8901 ????
You can't use native find mode to enter criteria in one field and enact an OR search.
Al least not to my knowledge.
Not without going to extremes....
You could probably put the values in list() format into a global field and leverage a relationship between the global and the serial number field to go to a proper record set
You are correct, what you want to do cannot be done. That's why you keep finding suggestions to automate the process by scripting it. By scripting, you can paste such a list of values into a global text field and the script can parse the criteria into individual find requests.
An alternative approach if you have several values separated by returns is to set up a relationship between the field into which you are pasting the data and the table of related records that you want to pull up. A portal or a script's Go To Related Records step can be used to display the matching values.
Ok, I have to accept the truth. LOL. Can you please give me an example of how to do this.? If not I understand.
paste serials into a global field
SetVariable($List; Substitute(global field;["-";"¶"];[" ";"¶"];[";";"¶"];[",";"¶"]) // change delimiters to LineFeeds
SetVariable($ListCount;ValueCount($List) //find out how many loops to execute
EnterFindMode (no pause)
SetField(Serial; GetValue($List;$Count) //get the serial# from designated position
ExitLoopIf($Count > $ListCount) // bail out of loop when all serials have been input into the Find
Or you can use a relationship once you have used substitute to get returns to separating the individual ID's as shown by StephenWonfor.
LayoutTable::IDListFIeld = TableToSearch::IDField
then a portal can list the matching records or you can use Go To Related Records in a Script to pull up a found set of those records. (And the substitute function could be put in as an auto-enter calculation on the IDListField.
Not saying one method is better than the other, just listing some options that are possible.