The settings “maximum number of records displayed” and “records per page” on the mobile device menu item, is created to help avoiding performance related issue’s. Let’s assume I would not populate these fields and I would have numerous workID’s open, these work id’s need to be queried all at once. Setting a limit on the max number, would avoid me having to query too many records. Having the records per page would than just outline how it is displayed on the mobile device (non scrolling), in this case a mounted terminal, or re-query a subset of data.

Having this terminal in place (45 forklift drivers) assists the warehouse worker to have a clean, (let’s say) 10 / to 12 record overview, and besides this, move back and forwards to next pages for a total of 50 to 60 work id’s. This would surely not result in performance issue’s? Does it? Not setting any max number, and or records per page, would, to me, clearly result in performance issue’s.

I understand that scaling will adjust the screen (dynamically), but also introduces “scrolling”. This would have been eliminated by using the next and or previous buttons. I would assume that having a button “next” which will query a subset of workId’s (let’s say 10 to 12), is faster in response than showing a list of 50 to 60 workID’s