You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Transactions aren't designed to be purchase and sales orders; they're more like modeling simple inventory transactions.
But while creating a procurement transaction, the form kind of looks like the products will be purchased for the given amount of money, which is nonsense, since what we're showing is based on the registered price of the products in our own system.
Adjust the form while keeping the following in mind:
Would be nice if we didn't have to complicate it further and could still use the same form for sales and procurement.
Transactions should be kept as inventory transactions, and we shouldn't overblow this sample app with PO and SO creation, separate purchase price, etc., because it would be too much trouble to model it nicely, and not doing that would make it look stupid.
But still keep showing prices in some way, because that adds at least some visually appreciable complexity to the form.
The text was updated successfully, but these errors were encountered:
Transactions aren't designed to be purchase and sales orders; they're more like modeling simple inventory transactions.
But while creating a procurement transaction, the form kind of looks like the products will be purchased for the given amount of money, which is nonsense, since what we're showing is based on the registered price of the products in our own system.
Adjust the form while keeping the following in mind:
The text was updated successfully, but these errors were encountered: