As for the question button or on_change: I have always been amazed (and annoyed) at the need to press the update button in order to have your taxes computed.
Having the user needing to press a button carries the possibility that he/she will forget this. With not computing taxes this error is very obvious. But with the change in fiscal position, I think the odds that users once in a while forget this are very high.
If it ever happens that a user changes a fiscal position by accident (and saves the form before realising his/her mistake), just changing back the fiscal position will easily revert taxes and accounts. And yes with a few hundred lines this might take a moment. But what are the odds that AND an invoice will have > 200 lines AND the user will change the fiscal position by mistake?
Thanks Alexis for updating the module.
As for the question button or on_change: I have always been amazed (and annoyed) at the need to press the update button in order to have your taxes computed.
Having the user needing to press a button carries the possibility that he/she will forget this. With not computing taxes this error is very obvious. But with the change in fiscal position, I think the odds that users once in a while forget this are very high.
If it ever happens that a user changes a fiscal position by accident (and saves the form before realising his/her mistake), just changing back the fiscal position will easily revert taxes and accounts. And yes with a few hundred lines this might take a moment. But what are the odds that AND an invoice will have > 200 lines AND the user will change the fiscal position by mistake?