Wrong allocation date stops accounting

I didn’t think to visualize it to get at it but to avoid irritation because of taking a date which is nowhere shown.

I think you can get the information instantiating the MPayment or MInvoice, no need to visualize the DateAcct - in most cases is the same DateTrx.

Hi ,

I agreed that’s no good idea, to use the patch.

I had a look at Allocation.calculatePayment and Allocation.calculateInvoice and the problem is, that both functions don’t have the DateAcct at hand. So it’s a bit more to do and I think the DateAcct should be visualized, too. At the moment I’m out of time but if nobody else does in the meantime I’ll take care of it later.

- the patch suggested in the description is precisely changing the date at model level, so the user fills a date in the form and the model saves a different date.

Maybe the change must be done better at Allocation.calculatePayment and Allocation.calculateInvoice where both methods calculate and set the variable allocDate

Regards,

Carlos Ruiz

Hi ,

I think the broken link is not really of interest, because:

• as you wrote it’s no good idea, to change the allocation date behind the scene

• the proposed change can be seen in the description