Product Update Blog (moved)

This blog is no longer being posted to. View recent updates at the Product Changelog page.

Cashflow Transfer Forecast Event Bug Fixed

Posted on by James

We've deployed a patch for a bug which was identified in the Cashflows page, where the rows for both the income and expense parts of a transfer event would be mis-assigned to the wrong calendar. The issue was because the cashflow rows were always being assigned to the first calendar which had any forecast event with the same title in it.

For example, if you have a "Repayment" transfer event going from a Checking calendar into a Credit Card calendar, then both the income and expense amounts for "Repayment" would appear in one of the calendars only - the one that was created first.

The fix means that we check that the category and type (income / expense) matches the first calendar found, and if not, we find the one that does.

So, given that the first calendar is Checking, and we're adding an cashflow income row for "Repayment". We find that the "Repayment" forecast event in the Checking calendar is an expense, so we look for a calendar with a "Repayment" income forecast event and use that - and we find it in the Credit Card calendar.

A caveat with this fix is that if you have two calendars with forecast events of the same title and type, then the cashflow row will again only show in the first of these calendars.

For example, both the "Credit Card 1" and "Credit Card 2" calendars have a "Repayment" income forecast event going into them. In the cashflow statement, the figures will only show as assigned to "Credit Card 1".

The fix for this issue is complicated and in depth, and requires some re-writing of some core areas (as we'd need to combine numbers within a cashflow row, depending on the selections on the right hand side - instead of showing / hiding them).

So for the moment, one work-around is to name each of the categories ("Repayment") to be different for each of the calendars ("Repayment CC1", and "Repayment CC2"). Another alternative is to ensure that the calendars affected are both activated (e.g. "Credit Card 1" and "Credit Card 2") when viewing the cashflows for either, ensuring the numbers will be correct.