Argument cannot be null

[wtben]

When processing order 160816174411618 in C&P Virtual Terminal, C&P successfully created the opportunity in SFDC but threw back the error "Argument cannot be null." Also, this transaction was to fulfill a pledge (a1Pd0000003JnAX) but the pledge remains in C&P Pledge as if unfulfilled.

Can you help me troubleshoot this error and identify why the pledge was not fulfilled in SFDC? You have access to 00Dd0000000borB for the week.

[CnP.Support]

Good day wtben

We reposted the transaction & it is fine in your instance. Please double check.

Also- please note that your instance is not up to date. Let us know if you wish for us to upgrade your instance.

[wtben]

Thanks! I had tried reposting from C&P Data in SFDC and it didn't work. Did you repost via C&P Connect instead or was there another avenue that worked for you. Also, can you explain the meaning of the error and how to interpret it?

[wtben]

Also, the donor reported getting our autoresponder 4 or 5 times, however the Autoresponder Log indicates the letter was only sent once. Any idea why there might be this discrepancy?

[CnP.Support.AM]

Good day @wtben,

We have re-posted the data within the Salesforce under C&P Data. Would you please share the order number so that we can review it?

Please note that due to re-posting the data the Autoresponder will fire if the the condition satisfied.

[wtben]

I was asking for clarification because I had previously tried reposting via C&P Data and the error was repeated. That is, on my first visit to the data, Message read Argument cannot be null. After reposting, both Error message and Previous error message read Argument cannot be null. After your repost, Message says successfully transacted and Previous error message is still the same.

I'm trying to troubleshoot why the error continued to appear for me but not for you. I'm also still interested in the meaning of the message. Can you explain?

Additionally, there were three posts here: the initial transaction from Virtual Terminal, my failed attempt at reposting, and your successful attempt at reposting. However, even before you reposted, the constituent said she received the autoresponder four or five times. Yet, the log only indicates one send attempt on the order (whose number I posted at the top of this thread). Can you explain the discrepancy? When reposting a transaction and triggering the autoresponder again (if checked), does it fail to log the subsequent message? Is this a bug?

Thanks for your insights!

[CnP.Support]

Good day wtben

The logs track the incident of a Transaction as Id'd by Salesforce and not the order number. So a Salesforce Transaction ID is being tracked. When you repost the transaction it will delete all previous footprints of the transaction and posts it again resulting in a new Salesforce ID for the transaction so the log now shows the history of this ID.

Given that you have deleted the old transaction by reposting it the history has been reset to 0.

Hope that answers the question.

[wtben]

Hi. A transaction on a recurring subscription (order #1608271950104888728) has erred with the same "Argument cannot be null" message. Can you please explain what this means and which argument it's referring to? Like last time, I tried reposting and it got the same error again. Nonetheless, the desired opportunity was created. Yet, the donor should have received an autoresponder but that message does not appear in the log.

[CnP.Support.AM]

Good day @wtben

We reviewed your instance and noticed that the above issue is due to the Pledges you have in your instance. We noticed that there is NO value in Remaining/Excess Balance in most of the Pledges you have in your instance which is causing an issue and throwing an exception "Argument cannot be null".



Since, Remaining/Excess Balance value is dynamic, we are wondering and want to know how you are creating those Pledges?

Looking forward to hearing back from you.

[wtben]

We usually receive pledges on paper pledge cards at our events. We shifted from creating Opportunities to creating C&P Pledges in hopes that when donors fulfill their pledges, the pledge records will get fulfilled automatically. I searched the manual for an entry about properly using C&P Pledges and couldn't find anything. We enter them manually via the C&P Pledge tab.

There aren't a lot of fields to choose from when adding or editing a pledge. Initially, we only completed the required fields. After correspondence with Kamran about some issues that cropped up, we learned the value of checking Allow Excess Amount (in case the donor ends up giving more than their pledged amount). We also started using SKUs more consistently and needed to enter one in the SKU Condition fields.

I have no idea why any of our pledges list a Remaining/Excess Balance. It's only notable that each of the three with a negative balance was created in June or later. Is it possible that an updated version of C&P changed this internal behavior when creating pledge records? I don't know what makes a few of the pledges unique enough to have zero balances instead of nothing listed. Since the record editor doesn't let me enter in this field, I've never touched it.

Is there a recommended method to creating pledge records? How does one resolve the empty Remaining/Excess Balance fields? What aren't you telling me?

[CnP.Support.AM]

Good day @wtben

Strange! the way you described of creating pledge is correct but why the pledges are showing with null/$0 value for Remaining/Excess Balance. However, we have manually fixed those pledges in your instance.

We have tested and unable to duplicate it in our test instances. We have created a pledge in your instance as well and all is working as expected. Please see if you find any issues for future pledges and let us know so that we can continue to investigate further.

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