HI Mark, nice to hear from you again. We deal with many clients, and any client can at any time ask us to take care of multiple requests. Each request is identifiable by what we will call a "serial "number", but there are potentially thousands of "serial numbers", and keeping a central database of all of them would be a waste. We manually input several numbers at a time into a multi line text field, but then, almost immediately, the project will split, and the developments for each serial number must be tracked individually.
For when things don't have to be done on the fly, I've arranged a child table in which there is a lookup field for all the serial numbers, and a formula text field which by default contains all of the serial numbers, but is replaced by only several when those are copy/pasted into a "work on these serial numbers" text box. The purpose of this arrangement is that 50% of the time, all serial numbers do follow the same flow, so the default setting eliminates the need to copy/paste in these cases.
My main issue is when things have to be input quicker, as some situations demand, where the "copy, paste, and start a new child record for the other serial numbers(s)" procedure is a but too bulky. That is why a multi choice, or a multi select, would be ideal.
