Thanks for the detailed feedback.
Have considered the first alternative you suggested, but there is a challenge with this approach. The results returned by the endpoint for each call is restricted to the
limit supplied which may affect accuracy. For instance, say the total number of past orders is 100, the first call returns 10 results, then this result is sorted on the frontend. The challenge this poses is that the newly sorted result might be incorrect because it was based on the 10 results returned by the first call. When a second API call is made, we get another set of 10 results which is sorted independent of the initial 10 results.
The better fix you suggested would be helpful in this case. However, that is outside the scope of our current Order Entry UI implementation. Could we get backend support from the community to implement this?
cc: @dkayiwa @wyclif @mogoodrich @kodero