Erik Huelsmann
Erik Huelsmann
> If, as I suspect, `Update` applies to the invoice, and `Save` to the payment information, there should be two sets of buttons---one above the payment information, for actions on...
There's a mismatch of expectations here: "Update" similar to "Recalculate"; "Save" is the only function which will *Save* the invoice or transaction. I'll consider if "Update" should be renamed to...
When bringing goods into Workflow, this item will be easy: the history will indicate when the item has been updated last. In that case, we don't need this drop down...
@promasu actually, #8947 is a PR, not an issue. I'll agree that this is a duplicate of #8162 .
Publishing the version with the fix will be really helpful: it's been like this for months now.
@Half-Shot any chance of having version 1.6.26 published on Google Play? These replies not showing are quite crippling: the mentioned workaround of long-pressing only works for short responses.
At this point I'm convinced overpayments have never worked to a level that is useable. I think we shouldn't advise people to use it until we have reimplemented it.
See the issues in the linked project for more context of that statement.
Duplicate of #4588 ?
This is exactly why payments, overpayments and AR/AP should be separate transactions. Currently, they are not...