A bit of a workaround, but why not create all OrderDetailsTable objects before opening the page?
This saves the trouble of managing on change events.
Probably there is no association set between the OrderDetailsTable-object (usually named ‘Orderline’) and the Product-object.
My approach would be to, upon opening the page, create the order-object, create a non-persistent entity with all product-objects that you want the user to choose from showing name, number and quantity and have those products be associated to the order that the user is creating. The onChange will still do its magic and keep the quantities in view.
Domain Model for the Application is attached here
Page Structure for the page taking orders from the user, the {Name} comes from a Database which is filled by a Rest API and has static values (Name,Price)
Your JsonObject has many OrderDetailsTable-objects that it can refer to, therefor the view OrderDetailsTable is empty and the OnChange will leave it empty again.