Holger Brunn
Holger Brunn
ah, you need to set a customer on the project(s) you want to invoice. A better error message about that would be nice indeed
I take you suggestion as the opinion of a single OCA member, given we have two approvals and you're a little bit late to the party ;-)
runboat build is fixed in https://github.com/OCA/bank-statement-import/pull/468
I can't really solve conflicts here because this branch is part of a very tightly pinned buildout. Did the rebase on a new branch and closed this PR ping @MPishpecki
what do you think about the argument that we have `account.move.line.blocked` and the idea of this module is to extend the concept of stuff being blocked?
so oca's imperative is to lose the `b` everywhere?
consider we have a setting of GMT+2, we set the pulling to daily, and the next run date initially to 2021-09-19 00:00:00 (CEST) with is 2021-09-18 22:00:00 (UTC). Then in...
well, but it doesn't. I've set the timezone there, and as you see from my debug description above, you will end up with wrong [balances per day](https://github.com/OCA/bank-statement-import/blob/12.0/account_bank_statement_import_online/models/online_bank_statement_provider.py#L251), because here in...
it is in the transaction date...
so how do we continue here? Do you think it's correct behavior that the statements show transactions from the UTC period of its date instead of the localized one?