Is there a way to work around this? And please explain why this change to omit functionality is a good thing. I find it counter-intuitive, but realize that somebody thinks otherwise, and would appreciate knowing why, and how I might use it to my advantage.
The reason for the change was a problem in the find related to omit.
Both before 3.1 and now, a find does not clear the omitted list.
The problem we fixed was that before 3.1, omitted records were shown in the find result, even though they were omitted.
Omitting another record after a second find would reduce the PK list to all found except the complete omit set.
for example,
find returns pk1, pk2 and pk3
omit pk2 → only pk1 and pk3 are shown
Before 3.1:
3) another find returns pk1, pk2 and pk3 (pk2 was omitted but is still returned)
4) omit pk3 → only pk1 is shown, pk2 and pk3 are omitted
Since 3.1:
3) another find returns pk1 and pk3 (pk2 was omitted and is not returned)
4) omit pk3 → only pk1 is shown, pk2 and pk3 are omitted
To clear the omit list, you can use loadAllRecords (CTRL-J).
Rob
Thank you, Rob, for the nice clear explanation! I really appreciate it.
Ctrl-J is not an option in our case, as the users of our solution have no access to menu items. I have instead prepended controller.loadAllRecords to all methods that find (list view filters, find all, export while excluding marked records, etc.). Does the job!