Revert SendReceipt to true for all donors, possible?

[bigbluepancake]

Hi, initially had we set SendReceipt to false on our donation form. This caused donors NOT to receive the CNP system receipt.

A few months ago, we changed SendReceipt from false to true.
So, from that day onwards, new donors will receive CNP system receipts. That's good.

However, there were many old donors who signed up for recurring donations while SendReceipt was false.
Even if SendReceipt is set to true now, they will still not get CNP receipts in their future scheduled deductions.

Question: For these old donors who signed up for recurring donations when SendReceipt was set to false - is it possible for CNP to internally set their SendReceipt to true, so that future deductions will cause the CNP receipt to be sent to them?

[CnP.Support.MA]

Good day bigbluepancake :

Yes, you can change "Send Receipt" to true, at respective recurrings detail page.

Please see the following KB article: http://help.clickandpledge.com/customer/en/portal/articles/2598285-connect-transactions#How to Edit/Update a recurring transaction



Please let us know if we can be of any further assistance.

[bigbluepancake]

Hi, thanks for the info. However, we have 760+ such donors. As you can imagine, doing it one by one via the UI is going to take a very very long time. Is there anyway to help us correct this in the database?

[bigbluepancake]

I also noticed that a problem with the UI: If the original donation did not fill out the State field, the page refuses to save any updates to Send Receipt because it deems State to be a mandatory field and so pops up an error message. So, it's impossible to proceed.

[CnP.Support.AM]

Good day @bigbluepancake

Yes, as of now it is mandatory field while updating the recurring information and it has to be updated manually.

Sorry for the inconvenience.

[bigbluepancake]

Hi, that means it's currently impossible for us to update Send Receipt, even via the dashboard. Is there any plan to fix this?

[bigbluepancake]

Or is there any way to raise a ticket for this to be fixed? This is quite important because State doesn't seem to be speced in the FaaS API as a required field (and perhaps, rightly so?). Yet, at the validation in the dashboard it suddenly becomes mandatory and thus blocks out any possibility of updates via the dashboard. This completely breaks the update functionality.

[CnP.Support.AM]

Good day @bigbluepancake

I have discussed this with our developers and they have considered to make those fields NOT mandatory. Hopefully in the upcoming release it will be addressed.

Sorry for the inconvenience.