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
Fundraising Matching #5406
Comments
We also ran into this issue for a specific batch a few weeks ago. There were several transactions that were either normal giving contributions but ended up getting attributed to a group member in a fundraising group or fundraising donations that ended up attributed to the wrong group member. We tried using the Fundraising Matching tool to make the corrections; however, the changes would not stay after we saved and then refreshed. It seemed like we could sometimes make edits or new matches but could never remove a match. We ended up having to get help removing the links using SQL to detach the transactions. We updated to 14.1 on 3/8/23 (currently still on this version), and we saw this issue on 3/23/23. |
Similar to this issue: #5636 |
…ed reloading the page after saving to make a new selection. (Fixes #5406)
Description
Our finance team was matching a couple of batches in fundraising matching, and went back in to adjust one of them. The new group/person would not save but would revert back to what it was. If you hit refresh on the browser and did it again, it would save fine. This would also happen with some new matches as well.
Expected Behavior
After matching each transaction in the batch that the group and group member that were selected would be saved for the group. If they are updated to a different group member that it would also save that update after making the new selection and hitting save.
Actual Behavior
After selecting the group and group member for a transaction, and hitting save the group and group member would be chagned to a different one. This happened when trying to adjust a previously saved match or when adding new ones. When adjusting one you could hit refresh on the browser, make the update again, and it would then save correctly. Before any more matching you would have to refresh again.
Steps to Reproduce
Rock Version
14.2
Client Culture Setting
en-US
The text was updated successfully, but these errors were encountered: