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
With #2188, we gained the ability to delete records from the database tables. However, when a user deletes a voucher that is a reversal, it does not toggle the "reversed" flag on the underlying table. This means that cash payments and invoices are still marked as "reversed", even if the voucher has been deleted.
This is a corner case bug. It should be fixed as soon as possible.
The text was updated successfully, but these errors were encountered:
This commit updates the voucher delete method to undo the "reversal"
flag on the reversed record if the voucher has been removed. It is
currently a naive method - simply attempt to remove the value if it is
present. This can be improved in the future by checking the transaction
types first.
ClosesIMA-WorldHealth#2207.
This commit updates the voucher delete method to undo the "reversal"
flag on the reversed record if the voucher has been removed. It is
currently a naive method - simply attempt to remove the value if it is
present. This can be improved in the future by checking the transaction
types first.
ClosesIMA-WorldHealth#2207.
2220: fix(vouchers): undo reversals on delete r=DedrickEnc a=jniles
This commit updates the voucher delete method to undo the "reversal"
flag on the reversed record if the voucher has been removed. It is
currently a naive method - simply attempt to remove the value if it is
present. This can be improved in the future by checking the transaction
types first.
Closes#2207.
With #2188, we gained the ability to delete records from the database tables. However, when a user deletes a voucher that is a reversal, it does not toggle the "reversed" flag on the underlying table. This means that cash payments and invoices are still marked as "reversed", even if the voucher has been deleted.
This is a corner case bug. It should be fixed as soon as possible.
The text was updated successfully, but these errors were encountered: