New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows 1.5.21 has calculation error in account view #5122
Comments
HI Mark
It is the balance at B, I'm viewing all transactions and I'm sorted on
descending date.
…On Fri, 23 Sept 2022 at 08:38, Mark Whalley ***@***.***> wrote:
When you say 'not included in the balance' what do you mean?
[image: CleanShot 2022-09-23 at 08 34 17]
<https://user-images.githubusercontent.com/487345/191912241-d438de4f-e120-4786-8998-cfc7fd220c73.png>
Is it the balance at A or B in above screenshot. The value at B is
dependant on how you sort the transaction view.
—
Reply to this email directly, view it on GitHub
<#5122 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKZJA7WE3UADKYXUW2DOUZTV7VM7JANCNFSM6AAAAAAQTW4IGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
As noted, the balance displayed will differ depending upon sort. Descending and Ascending date will have different results. With descending date the first item (latest date) will hold the balance, and with ascending date the last item (latest date) will hold the balance. Is this what you are seeing. |
HI
If I sort date,ascending I see a different value in the balance column (B
from your first screen shot) from when I sort date,descending. The balance
from date,ascending is the correct value.
…On Fri, 23 Sept 2022 at 09:09, Mark Whalley ***@***.***> wrote:
As noted, the balance displayed will differ depending upon sort.
Descending and Ascending date will have different results. With descending
date the first item (latest date) will hold the balance, and with ascending
date the last item (latest date) will hold the balance. Is this what you
are seeing.
Descending date
[image: CleanShot 2022-09-23 at 09 05 42]
<https://user-images.githubusercontent.com/487345/191917249-df9ead34-c9a8-4cee-af2d-a64d237f749b.png>
Ascending date
[image: CleanShot 2022-09-23 at 09 06 09]
<https://user-images.githubusercontent.com/487345/191917503-e88d9140-a708-4297-9fc6-93b5d1bcb9cd.png>
—
Reply to this email directly, view it on GitHub
<#5122 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKZJA7VFAXR5O4SN4NMM5CDV7VQUVANCNFSM6AAAAAAQTW4IGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Can you please share a screen shot of what the issue is, I'm struggling to help without this. |
It may be related to a 'sort refresh' error (#5108) in the current build.... Does the build here help? |
I have installed the beat version 1.5.22 and the behavior is unchanged.
This is the view and sort I normally use. The true balance value is 1482.44
for September 23rd
[image: image.png]
I have move the £175.00 credit entry to September 22 and the balance is now
correct.
[image: image.png]
I have restored the credit balance date to September 23 and move the £10
withdrawal entry to September 22 and the balance is correct.
[image: image.png]
The 4th screen snip is the date,ascending view with the two transactions I
edited above from today restored to todays date.
[image: image.png]
…On Fri, 23 Sept 2022 at 09:42, Mark Whalley ***@***.***> wrote:
It may be related to a 'sort refresh' error in the current build.... Does
the build here help?
https://ci.appveyor.com/project/moneymanagerex/moneymanagerex/builds/44859308/job/v3t4q2w20wm4me62/artifacts
—
Reply to this email directly, view it on GitHub
<#5122 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKZJA7SXWGZXYZNQD3CVTV3V7VUOFANCNFSM6AAAAAAQTW4IGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Images not visible. Please don't respond by mail. Can you post here: #5122 |
picture 1 is snip3 |
Have reordered the images! |
@n-stein Yes, this maybe indeed be the case. @mike9665 has the ID field hidden. There was some discussion around users possibly being confused by the secondary sort when we originally looked at this. #4690. Maybe we:
I favour option (2). |
@whalley I think option 2 would work, but breaks the consistency of the "Secondary Sort" behavior. You couldn't achieve the below view where secondary sort is by Payee and primary sort is by date: What about changing the behavior of the Model_Account::transaction method to sort by secondary sort order followed by date instead of the default ID then date here? moneymanagerex/src/model/Model_Account.cpp Lines 198 to 199 in b647e45
|
I feel the main issue here is with users who don't need, or more likely don't realise, that the secondary sort function exists. They just click DATE and assume that things are sorted in chronological order which means DATE (and ID to put some order to the the IDs on the same date). In your example with DATE/PAYEE order it is going to cause confusion as the Balance against ID 53 does not match the headline 'Account Bal:'. Note this DATE/ID order is used across the application to represent the account balance. |
I think the DATE/PAYEE order is only confusing right now specifically because ID 53 does not match the headline balance. If the balance was calculated by DATE/PAYEE as displayed rather than DATE/ID then 53 would contain the headline balance, no? I see how changing the DATE/ID function of Model_Account::transaction could cause issues due to its wide usage. We could instead include the secondary and primary sort between these two lines: moneymanagerex/src/mmcheckingpanel.cpp Lines 160 to 161 in b647e45
|
I'll let others contribute to the discussion. I'm a little wary about changing the balance calculations as it may cause further confusion. I think there is simplicity/comfort in knowing that the balance line against a transaction remains constant regardless of sorting. |
We did discuss this along the way. It is the logical thing to do because, as I assert here #4690 (comment), I think relatively few people have a need to do anything other than the standard Date | ID sort. I still think the idea of having a visual indication of the secondary sort column would be helpful. Maybe not the dashed up/down arrow suggested previously but some way of knowing what the secondary column is - perhaps a tooltip that is shown when you hover over the primary sort column header? Not sure what's for the best. 1.5.21 sorting has stirred up a lot of comments! |
@grumpy235 Good spot, the secondary sort default before any setting is saved was also DATE. Have now set to ID. |
fix(#5122): secondary sort default is ID
The balance is ALWAYS calculated as on a bank statement, i.e. date (or more strictly DATE/ID) order. Having the balance displayed even when not sorting by date can often be useful as it still represents the balance when the transaction was posted. The secondary sort on teh column headers was not implemented to avoid confusion, it just shows the last (primary) sort order selected by the user. Having the primary and secondary sort displayed alongside the transaction view information gives further information.
No.
Where is anything described? We have no documentation that is kept up-to-date, there is no resource to do it. It would be great to have a technical author to write all this. |
It looks like the issue is not closed within 1.6.0 version. |
Discussed in #5121
Originally posted by mike9665 September 23, 2022
I updated from 1.5.20 to 1.5.21 and a deposit dated today is not included in the balance. If I change the date to yesterday the balance is correct. I have also fallen back to 1.5.20 and the balance is correct when the deposit is dated today.
Mike
The text was updated successfully, but these errors were encountered: