FinancialPaymentDetail Fields are Nullified when using ScheduledTransactionEditV2 #5585
Closed
1 task done
Labels
Comments
taylorbrooks
changed the title
sparkdevnetwork-service
added
the
Status: In Dev Queue
taylorbrooks
added a commit
to taylorbrooks/Rock
that referenced
this issue
Sep 11, 2023
This was referenced Sep 11, 2023
shauncummings
added a commit
that referenced
this issue
Sep 14, 2023
…lost when modifying a scheduled transaction using the new V2 block for hosted gateways. (Fixes #5585)
sparkdevnetwork-service
removed
the
Status: In Dev Queue
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please go through all the tasks below
Please provide a brief description of the problem. Please do not forget to attach the relevant screenshots from your side.
When editing a scheduled transaction with the ScheduledTransactionEditV2 block AND you are NOT changing the payment method, two things happen:
ReferencePaymentInfoisn't being passed through to the FinancialGateway (see prior issue here)See an overview here: https://www.loom.com/share/16ef5e4459e544e3a112d9d7d7e545f4
Expected Behavior
When someone edits a scheduled transaction, using the same payment method, the payment method's details will persist and NOT be nullified and the ReferenceNumber on the ReferencePaymentInfo object gets passed to the gateway.
Actual Behavior
The payment method's details are being blanked out and the
ReferenceNumberis not passed to the gateway.Steps to Reproduce
See video above for steps to reproduce.
Rock Version
15.1
Client Culture Setting
en-US
The text was updated successfully, but these errors were encountered: