Announcement

Collapse

Information Needed

To help us with upgrading your instance please make sure to:
See more
See less

Payment Type string too long error

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Payment Type string too long error

    I spoke with Amanda during the live chat support hours with our issue and she told me to post here.

    We are having issues with some of our click & pledge transactions. When a user pays with an American Express Credit Card we receive an error message:

    "Upsert failed. First exception on row 0; first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, npsp.TDTM_Opportunity: execution of AfterInsert

    caused by: System.DmlException: Insert failed. First exception on row 0; first error: STRING_TOO_LONG, Custom Payment Field: data value too large: American Express (max length=15): [npe01__Custom_Payment_Field__c]

    The field "npe01__Custom_Payment_Field__c" is a managed field so we are unable to change the length and this error stops opportunities from being made. In NPSP Settings->Donations->Payment Mappings we have the Opportunity Field "C&P Payment Type" to the Payment Field "Custom Payment Field". This error only applies to "American Express" so Visa and MasterCard work fine since they are under the 15 character limit. Is it possible to change the mapping so it says "Credit Card" or "AMEX" instead?

    Installed Packages:
    Nonprofit Starter Pack Version: 3.99
    Click & Pledge PaaS Class Library 5.1703010003
    Click & Pledge Payment as a Service 9.1705100003
    Click & Pledge Events 5.1705020007

  • #2
    Good day cnpuser

    The issue is naturally with NPSP.

    see the error message:

    caused by: System.DmlException: Insert failed. First exception on row 0; first error: STRING_TOO_LONG, Custom Payment Field: data value too large: American Express (max length=15): [npe01__Custom_Payment_Field__c]

    Based on what I see: STRING_TOO_LONG

    it seems like NPSP has a field for credit card that does not accept "American Express" as a card type.

    You seem to have a custom field called: [npe01__Custom_Payment_Field__c]

    This is not a C&P issue - have you reviewed the NPSP fields? the error is NPSP based.
    Regards,
    Click & Pledge Support Department

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

    Join us @ the educational webinars: https://clickandpledge.com/webinars/
    Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
    Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

    Comment


    • #3
      I did see that it was an NPSP issue and before reaching out here I submitted a ticket with Salesforce. They said because this was a managed field it could not be changed and told me this was an issue on C&P's side since it populates the field. Is it possible to rename "American Express" to "AMEX" or change the field to just fill with "Credit Card"?

      Comment


      • #4
        Good day cnpuser

        We need to review this case with the development team and get back to you.

        It is interesting that NPSP decides to create a field that is smaller than the length of a legitimate credit card name, used all over the world and then says it is our problem ..

        We will review and figure out what we can do to help.
        Regards,
        Click & Pledge Support Department

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

        Join us @ the educational webinars: https://clickandpledge.com/webinars/
        Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
        Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

        Comment


        • #5
          Good day cnpuser

          We have contacted NPSP team to discuss this issue. We cannot possibly change the legal name of a credit card given our clients are using this in their triggers, etc. We have not had this reported before as nobody uses the mapping offered in NPSP for this field.

          Once we hear back from the NPSP team we will update this thread. You may want to remove the map for now until we have a resolution from them. American Express is 16 characters long and NPSP's size for this field is 15 characters.

          I am sure we will find a solution as both applications need to work seamlessly, but we also have to make sure we take the "right" path and not patch it for now. I hope you see the point.

          We will update this when we find out from NPSP as to what they will do.
          Regards,
          Click & Pledge Support Department

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

          Join us @ the educational webinars: https://clickandpledge.com/webinars/
          Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
          Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

          Comment


          • #6
            Good day cnpuser

            We just had a conversation with NPSP team and the following is the recommendation.

            You need to create a new custom field and call it whatever you want. Once it has been set up please map the payment type to that field.

            Hope that helps.
            Regards,
            Click & Pledge Support Department

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

            Join us @ the educational webinars: https://clickandpledge.com/webinars/
            Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
            Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

            Comment


            • #7
              Thank you for the help! We have created a new custom field to use for the time being.

              Comment

              Working...
              X