Skip to content
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

Transaction Matching Account Ordering Broken #5371

Closed
1 task done
SteveSwaringen opened this issue Apr 4, 2023 · 3 comments
Closed
1 task done

Transaction Matching Account Ordering Broken #5371

SteveSwaringen opened this issue Apr 4, 2023 · 3 comments
Labels
Fixed in v16.1 Type: Bug Confirmed bugs or reports that are very likely to be bugs.

Comments

@SteveSwaringen
Copy link
Contributor

SteveSwaringen commented Apr 4, 2023

Please go through all the tasks below

  • Check this box only after you have successfully completed both the above tasks

Please provide a brief description of the problem. Please do not forget to attach the relevant screenshots from your side.

Financial accounts listed on the right side of the Transaction Matching page should be ordered accounting to the FinancialAccount.Order property in order to facilitate easily finding the most frequent accounts. This was the case in V13.V14 now renders these accounts in FinancialAccount.Id order, making it very difficult for accounting staff to reconcile batches.The way it was (and should be):

imageThe way it is in V14 (and shouldn't be):

image## Expected Behavior
Financial accounts listed on the right side of the Transaction Matching dialog should be ordered by FinancialAccount.Order.## Actual Behavior
Financial accounts listed on the right side of the Transaction Matching Dialog are ordered by FinancialAccount.Id.## Steps to Reproduce
Go to page/311. (May be different on your installation, but this seems to be a "core" page that is the same on most installations.)## Rock Version
V14.2## Client Culture Setting
en-US

@SteveSwaringen
Copy link
Contributor Author

SteveSwaringen commented Apr 4, 2023

This issue was induced by modifications to the TransactionMatching.ascx.cs block that were part of this commit: https://github.com/lakepointe/Rock/commit/981f4d41777d043760559df07ef17c221be599d2#diff-08863471e16a228be6a6f00152141adfbbce797b21d1182ff318e82dd0ec2400

I don't pretend to understand why the changes in that commit broke the sort order (though I suspect it has something to do with not having an equivalent of the GetTree() call available on the FinancialAccountCache model). However, reverting those changes fixes the problem.

@sparkdevnetwork-service sparkdevnetwork-service added the Type: Bug Confirmed bugs or reports that are very likely to be bugs. label Apr 27, 2023
@SteveSwaringen
Copy link
Contributor Author

Apologies for posting the link to the commit merged into our repository. This is the commit in the Spark repository: 981f4d4

jonedmiston added a commit that referenced this issue Oct 4, 2023
@jonedmiston
Copy link
Member

Fixed this in the commit above. @SteveSwaringen would love to know if this solved your issue before v16.1 goes to alpha (soon).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Fixed in v16.1 Type: Bug Confirmed bugs or reports that are very likely to be bugs.
Projects
None yet
Development

No branches or pull requests

3 participants