Filter Error Example - Bug
I've reported this before and I haven't seen any change in behavior after a couple updates. Here is a simple, straight forward example of what I'm trying to do.
I have a transaction that I've classified as a Loan Receivable. I have several different entries in the register for Loans Receivable. For each transaction I enter a tag to identify that party the loan is to. When I filter on the TAG while in the Loans Receivable Asset account, I expect to see all the transactions associated with a tag that matches or contains the filter search entered. That is not the result.
The example attached shows the detail transaction that exists in the Load Receivable account along with the Search Filter filled in which yields no results. I have tried entering the search criteria with and without the square brackets and both ways yields no results.
Please advise if I'm expecting this to do something it was not designed to do or if it is a bug. I am running Linux system openSuSE, MoneyDance Version 2023.3 (5064)
MoneyDance_FilterError_Transaction.png
MoneyDance_FilterError_FilterResults.png
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by dwg on 24 Jan, 2024 04:34 AM
I'm a fellow user.
I think the square brackets [] might tell us what is happening. These indicate the entry comes from the other side of the transaction and is only shown here for information purposes, it is possible to have different entries in some field on each side of the transaction and this is one of those fields.
Hence the search cannot find the value when you search on it in the account where is shows inside square brackets because it is not really there.
2 Posted by dm_corsa on 24 Jan, 2024 04:49 AM
Agreed that that makes sense but it kind of renders the tag useless anywhere but the original entry, so you would have to 'retype' all the transactions on the other side of the transaction to get it to stick. Seems cumbersome to me.
3 Posted by dm_corsa on 07 Feb, 2024 02:52 AM
Another finding related to this. If there is no split on the originating transaction, then the Loans account properly reflects the entry and the Tag Filter option will pick up that transaction. However, if there are multiple splits, even just two splits, then it breaks, meaning the filter will no longer pickup the corresponding transaction. It's like a loop is missing somewhere to process the posting of the transaction along the way.
System closed this discussion on 08 May, 2024 03:00 AM.