Information Needed

See more
See less

Temporary Contact Error - Invalid Decimal: null?

  • Filter
  • Time
  • Show
Clear All
new posts

  • Temporary Contact Error - Invalid Decimal: null?

    Since updating C&P to the latest version, we've been getting a strange error message after processing Temporary Contacts. A screenshot is attached.

    From what I can tell, the system is still processing the gifts and recording them in Salesforce. But donation records created when the error message appears have a strange recurring reference number, even if the gift was not a recurring one. Here's an example: null-1608021013379460995-null

    Our organization ID is 00Do0000000KPWy and account access has been granted for one week. Thanks in advance for your help resolving this issue.
    Attached Files

  • #2
    Good day!

    I have asked one of our developers to review your instance. Will update you by tomorrow as they need to review the log files.
    Click & Pledge Support Department

    Join us @ the educational webinars:
    Live Support- read more:


    • #3
      Good day @kwolfe,

      We reviewed and noticed that the above transaction has been processed in the PaaS Version#9.4017 in which there was an issue with recurring reference number which has been addressed in the latest release version# 9.5011.

      You have upgraded to latest version#9.5011 on 8/4/2016. I don't see any transactions in your instance after 8/4/2016. We have processed on test transaction in your instance with name Account Verification Order#160805080403992 and see NO issues.

      Please review and let us know if you find any issues in latest release.

      Click & Pledge Support Department

      On Salesforce? Help us by rating our app: Click & Pledge Donor Management on AppExchange

      Join us @ the educational webinars:
      Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday:
      Are you on Salesforce? Join us at the Power of Us Hub:


      • #4
        We received a Temporary Contact this morning and were able to process it with no issues. It appears that this has been successfully resolved.

        Thank you!