Error: Data could not be saved The INSERT statement conflicted with the CHECK constraint CK_EVENTREGISTRANTPAYMENT_VALIDAMOUNT". The conflict occurred in database "XXXX", table "dbo.EVENTREGISTRANTPAYMENT", column 'AMOUNT'." - when adding payment

The following error may be received when attempting to add an additional payment to an Event registration:
Error: Data could not be saved. The INSERT statement conflicted with the CHECK constraint "CK_EVENTREGISTRANTPAYMENT_VALIDAMOUNT". The conflict occurred in database "XXXX", table "dbo.EVENTREGISTRANTPAYMENT", column 'AMOUNT'.
Follow the steps below to resolve: 
  1. Go to the event. You can see that designations tab is showing a conflict icon.
  2. Go to the Designations tab. Click Edit and then click Distribute Evenly.
  3. Save and you will see that the conflict icon is gone.

Steps to Duplicate

  1. Go to the main Events page and search for and open the event
  2. Select the Registrations tab and open the registration for the constituent
  3. Select Add payment, enter a payment amount, highlight the registration, select Add, OK, and edit the Receipt amount so it matches the payment amount
  4. Attempt to save the payment and receive the error 

Environment

 3.15

Was this article helpful?


Thanks for your feedback! Did this solve your issue?

Comments (optional):


Thanks for your feedback!
We're glad it was helpful but sorry it didn’t solve your issue. If you need assistance, click Chat with Support below.
We’re sorry to hear that. Please tell us why.

 I don't like how this works.

 The answer is confusing.

 The answer didn't match what I was searching for.

Additional Comments (optional):


Thanks for your feedback! If you need assistance, click Chat with Support below.
Thanks for your feedback. Help us make our products even better by sharing details in our Idea Banks or our online Community.
Thanks for letting us know. We'll work on clarifying the information in the article. If you need assistance, click Chat with Support below.
Thanks for letting us know. We'll work on updating the search engine to return more relevant results.