Information Needed

See more
See less

Error Report

  • Filter
  • Time
  • Show
Clear All
new posts

  • Error Report

    I received two Error Report notifications on 7/12 & 7/13, please advise on how to resolve.

    Order numbers are:
    - 1507132242538464707
    - 1507121132183907517

    Org ID is 00Di0000000H8fk and I have granted login access.

    Error message in notification reads:
    "System response: "Upsert failed. First exception on row 0; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, The Contact Id supplied in the Contact Id for Role field was invalid. Please use a valid Contact Id.: []"

    When I click on the link provided in the notification, I get a message in salesforce that says: "The record you attempted to access has been deleted. The user who deleted this record may be able to recover it from the Recycle Bin. Deleted data is stored in the Recycle Bin for 15 days. " However, there is nothing in my org's recycle bin that matches the Contact.

  • #2
    ** I moved this post to the Salesforce channel. Please post the messages to the correct channel to minimize delay.

    Good day!

    Based on the C&P Data log file you have 2 errors that were caused today and prior to today all had worked correctly. Have you made any changes to your validation rules?

    Here is the error:
    Click image for larger version

Name:	2015-07-15_11-11-08.jpg
Views:	19
Size:	50.7 KB
ID:	17957

    The error indicates a validation rule is being violated and as such Salesforce is blocking the creation of the record.

    If you cannot figure out what is causing this we can request a developer to review and try to assist you with this. This is a custom rule created by your organization and not any 3rd party app.

    Please let us know if you need us to determine the validation rule that is generating this error.
    Click & Pledge Support Department

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


    • #3
      I have not created any validation rules (I don't even know how) so yes, please help me figure out which rule is causing the error.


      • #4
        Good day!

        We reviewed your instance & realized the issue is an old issue and a known bug with NPSP 2.x

        There has been many discussions in the HUB regarding this and NPSP will not resolve this in 2.x as they have already upgraded to 3.x. The problem is with Contact Roles.

        Please see this thread in the POU-HUB:

        We are told that NPSP will not fix this issue and they ask all clients to move to NPSP 3.

        Sorry we can't be of more help. The only solution is upgrade to the latest update.
        Click & Pledge Support Department

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