quantity.
I have explained my approach in combination with more info on the challenge on a gist.
https://gist.github.com/mimidotsuser/896df9f8e3a5bcdaa8e3cbb2062f480a
My approach works well during the creation and update of each record for all the steps.
But when someone deletes a document e.g. a purchase request, my balance goes into limbo.
Is there a better database design to avoid or minimize the chaos?
Anyways, you say your current problem is when purchase request is deleted. So that means you should get notified when it happens so you can decrement Restock qty?
Обсуждают сегодня