Announcement

Collapse

Information Needed

See more
See less

Salesforce custom trigger on Opportunity throwing error in CnP_PaaS.addCorresCont

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

  • CnP.Support
    replied
    Please note that version 4.11 was released recently. We strongly recommend upgrading to the latest release.

    The upgrade link is available in the Release Notes section & in the Latest Release link in this forum.

    Leave a comment:


  • CnP.Support
    replied
    Thank you for getting back to me so quickly.

    We are releasing version 4.10 on Monday. Version 4.0 had an issue with large recordsets and it was fixed in 4.1.

    You may upgrade to 4.6 through the link in the forum:

    http://forums.clickandpledge.com/articles/api/faas

    If you wait till Monday we will have release 4.10 which has many new features.

    Please let me know how you wish to proceed. Of course if you upgrade to 4.6 the error will go away.

    Leave a comment:


  • rbowen
    replied
    Installed Package
    Click & Pledge Payment-as-a-Service
    Available in Versions
    4.0 - Current

    Leave a comment:


  • rbowen
    replied
    Not sure where to find version number. In Salesforce, under the CnP custom objects, it notes:
    Installed Package
    Click & Pledge Payment-as-a-Service
    Available in Versions
    4.0 - Current

    Please let me know if the version number is found elsewhere.

    Leave a comment:


  • CnP.Support
    replied
    Good day!

    What version of the application are you running? are you on 3.15?

    Leave a comment:


  • CnP.Support
    replied
    Good day!

    I will direct this question to our developer team and will get back to you with an answer. We need to research your errors.

    Sorry for the inconvenience.

    & version 4.10 is due out tomorrow (hopefully!).

    Leave a comment:


  • Salesforce custom trigger on Opportunity throwing error in CnP_PaaS.addCorresCont

    We're using the NPSP, and have created a custom trigger on the Oppportunity object, which is throwing an error during the Validate Deployment step, when moving the trigger to production. The trigger pulls data from the Custom Question object (related to the Transaction object), and writes the value to some custom fields in the Opportunity object.

    The trigger and test coverage runs corrrectly and completely in a sandbox environnment (which was just updated from production). However, the code (test coverage) fails when trying to deploy to production.

    Here is the pertinent error:

    -----------------------------------
    CnP_Custom_Question_Loader_TestSuite.verify_CnP_Cu stom_Question_Loader_Bulk System.DmlException: Insert failed. First exception on row 0; first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, CnP_PaaS.addCorresCont: execution of BeforeInsert

    caused by: System.QueryException: Non-selective query against large object type (more than 100000 rows).
    ----------------------------------

    This seems to be an error in the addCorresCont trigger deployed in the C&P managed package. Since we cannot view the code, we do not know what is throwing this error. The error occurs on the line in our trigger that creates a new transaction object. We have more than 100,000 Contact records in production, and only 10 in the sandbox.

    Additionally, after running all tests in production, the following failures occur with other C&P managed code:

    CnP_Redirect_ControllerTest (testRedirectController method) fails with a System.DmlException (same failure we were getting in the above example of our trigger).
    CnP_Transaction_Detail_ControllerTest (testRecurringDetailController method) fails with same System.DmlException.
    Credit_TransactionsTest (testCreditTran method) fails with same System.DmlException.
    SaveClass_Test (testSaveClass method) fails with same System.DmlException.
    TestdataConvert (TestdataConvert method) fails with same System.DmlException.

    We've searched through the online manual, but there are no references to the triggers that run in the managed code.

    We need some help in determining why all of these methods in CnP's managed code are throwing DmlExceptions.

    Thanks for any help in advance.
Working...
X