Fundraising Matching Block does not allow clearing previously matched transaction

[azturner]

Description

In the fundraising matching block, if you assign a transaction to a specific group/member, you cannot then clear that selection. The UI allows clearing the value, but after clicking Save, the group member re-appears in the selection for that transaction.

Actual Behavior

Clearing the group member selection does not save.

Expected Behavior

If you clear the value in the UI, it should save the cleared value.

Steps to Reproduce

• Setup at lease one fundraising opportunity group with at least one member.
• Add a financial batch and transaction.
• Go to the fundraising matching page
• Select the batch that was just created
• Match the single transaction in the batch to the member of the fundraising opportunity group
• Save changes.
• Clear the group member selection
• Save changes
• Group member re-appears after the change.

Issue Confirmation

• Perform a search on the Github Issues to see if your bug or enhancement is already reported.
• Try to reproduce the problem on a fresh install or on the demo site.

Rock Version

v12.8, v15.1

Client Culture Setting

en-US

[jonedmiston]

Similar to this issue: #5406

[tbunney]

I just tested this in Alpha version 1.16.1.1 and I can still not clear a previously matched transactions.

I cleared them, then clicked Save. Refreshed the page, and they were showing again.

[chead4]

@tbunney Hi Tiffany I am unable to recreate this issue on v16.1. If you could supply a video that would be very helpful as I may be doing something different than you are.

[tbunney]

Here is a link to a video to show you what I mean: https://www.loom.com/share/b440d5b994e04e81ab6377d6b51e24c3

On Wed, Dec 6, 2023 at 3:58 PM Colleen Head ***@***.***> wrote: @tbunney <https://github.com/tbunney> Hi Tiffany I am unable to recreate this issue on v16.1. If you could supply a video that would be very helpful as I may be doing something different than you are. — Reply to this email directly, view it on GitHub <#5636 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AI7UWEXVBHETLVDRYDERPETYIDL6BAVCNFSM6AAAAAA6F7QVUOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBTGY3TSOBQHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast, a leader in email security and cyber resilience. Mimecast integrates email defenses with brand protection, security awareness training, web security, compliance and other essential capabilities. Mimecast helps protect large and small organizations from malicious activity, human error and technology failure; and to lead the movement toward building a more resilient world. To find out more, visit our website.

[chead4]

@tbunney Thank you for the video. I was removing the Group Member and not the Group in my test. I was able to recreate.

[nairdo]

@tbunney Just a quick update. We've put a new fix (39797d2) into the v16.1 alpha package for the round no. 2 testing which is about to begin. Please let us know if that does not resolve the issue for you or if you run into any troubles with this.