Not yet. What is the validation carried out on Units field in the orderEntry form. I keep on receiving illegal value when i inspect the element no matter what value i fill… and also which table is it looking up it data from or senting it data to. I will give in some 3 hours and if i still don’t get it working i will love to free up the issue So the sprint can complete in time. Frankly i didn’t expect this ticket to take this long. Also a little guide on the approach and what is possibly going wrong will be usefull. I’ve used this algorithm for sorting objects it works just fine but in this case i don’t know why it is not sorting… https://github.com/fanyui/openmrs-module-webservices.rest/commit/3bdd035fdaf1e555c30dcef66d5967f8a49a3128

Hi @harisu I have been looking into your code. I have been able to make a few adjustment to it and get it to work on the orderEntry OWA, which also required adjusting our url param from ...&t=drugorder to ...&type=drugorder

This worked for pastOrders which thus bring me to my question of how sorting should really work here. If the user is searching for inactive orders then it makes sense to sort by the date such orders were deactivated and if searching by active orders then the date they were activated should be used. What do you think? cc @darius@dkayiwa@kodero@fred@flavia@betty@zeze@geofrocker@wyclif

Yeah i would love to reclaim it. didn’t have the intention of abandoning the ticket except for the fact that it was taking longer and seems to delay the entire sprint. @larrystone just raised a pertinent design point in his post i dont know if that will also be taken care of or just going with the normal description of the ticket and updating based on his advice will be ok.

If the user is searching for inactive orders then it makes sense to sort by the date such orders were deactivated and if searching by active orders then the date they were activated should be used. What do you think?

I actually meant searching or better still fetching. A typical url would look something like .../orders?sort=desc&status=inactive.... The status parameter would help the backend decide the criteria for sorting (createdDate/stoppedDate for activeOrders/pastOrders respectively)