this shows the need for some deeper database design.
sometimes we need to record a history of changes.
as @Christiaan_Huizer, suggests, we need a history table to record past prices, and each order links to the row that was current at the time-of-order.
but a simpler method can also be used…
instead of getting the price of a product using a FORMULA, you could set the price in the order using a modifyRows() operation. this would copy the current product price into the order row. and it will not change in the future if the product price is changed. the modifyRows() operation needs to be done inside a BUTTON that gets pushed to create a new order.
good to read you took my suggestion serious, I wrote a blog about it.
in all my work this logic is applied (contact details, turn over, product prices, addresses, etc).
once you see how useful and important it is, it is hard to do it differently,
hi @Yalcin_Arsan , this is maybe difficult at first glance, but the principles applied are simple
per row you have product and a price with a time stamp.
you compare time stamps via a filter, it results in a list of values and you take the last one