Answers.Body: <p>Yes thats true, if you update certain parameters of existing pledge than it deletes all pledge payment and recreates it. Below are the parameters when changed deletes all pledge payments.</p>
  
  <ul>
  <li>amount</li>
  <li>frequency_unit</li>
  <li>frequency_interval</li>
  <li>installments</li>
  <li>start_date</li>
  </ul>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-08-15T22:43:06.080Z
Answers.Text: But there's no warning for the user, which causes the uninformed to destroy contribution history. I understand it works this way, but I don't understand why it's not considered a bug or why there is no work around. (is there a work around?)
Answers.UserDisplayName: LaurynnLowe
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-12-31T11:50:32.237Z
Answers.Text: actually it should 
  1. Keep existing pledge payment record.
  2. Delete un-paid (pending/overdue) pledge payment record.
  3. Re-calculate the number of installment based on new installment amount or frequency unit or interval change.
  4. Then add new entries of pledge payment.
Answers.UserDisplayName: Sunil Pawar
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-08-15T18:37:53.873Z
Answers.LastActivityDate: 2018-08-15T18:37:53.873Z
Answers.UserDisplayName: Pradeep Nayak
Answers.Body: <p>Can you check this PR</p>
  
  <p><a href="https://github.com/civicrm/civicrm-core/pull/13374" rel="nofollow noreferrer">https://github.com/civicrm/civicrm-core/pull/13374</a></p>
  
  <p>There seems to be a bug that allows you to change the payment schedule and wiping out the contributions in the process. The above patch will fix the same.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-12-31T09:41:19.320Z
Answers.LastActivityDate: 2018-12-31T09:41:19.320Z
Answers.UserDisplayName: Yashodha Chaku
Body: <p>Since upgrading to 5.3, we've noticed that Pledge amounts can be edited, which then deletes any payments made toward the pledge. </p>
  
  <p>In earlier versions, the Pledge amount could not be edited. (this is true with 4.6; I'm not sure about other versions)</p>
  
  <p>The only discussion I can find is a patch from a few years ago created for 4.7: <a href="https://issues.civicrm.org/jira/browse/CRM-17762" rel="nofollow noreferrer">https://issues.civicrm.org/jira/browse/CRM-17762</a></p>
  
Tags: <pledges>
Title: Editing Pledge Amount Deletes Payments
ThreadText: # Editing Pledge Amount Deletes Payments
  
  (Asked by: username_0 on 2018-08-15)
  
  Since upgrading to 5.3, we've noticed that Pledge amounts can be edited, which then deletes any payments made toward the pledge.
  
  In earlier versions, the Pledge amount could not be edited. (this is true with 4.6; I'm not sure about other versions)
  
  The only discussion I can find is a patch from a few years ago created for 4.7: <https://issues.civicrm.org/jira/browse/CRM-17762>
  
  **Tags:** pledges
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2018-08-15. Score: 1
  
  Yes thats true, if you update certain parameters of existing pledge than it deletes all pledge payment and recreates it. Below are the parameters when changed deletes all pledge payments.
  
  * amount
  * frequency\_unit
  * frequency\_interval
  * installments
  * start\_date
  
  > **Comments:**
  > **username_0**: But there's no warning for the user, which causes the uninformed to destroy contribution history. I understand it works this way, but I don't understand why it's not considered a bug or why there is no work around. (is there a work around?)  
  > **username_2**: actually it should  1. Keep existing pledge payment record. 2. Delete un-paid (pending/overdue) pledge payment record. 3. Re-calculate the number of installment based on new installment amount or frequency unit or interval change. 4. Then add new entries of pledge payment.  
  
  ---
  
  ### Answer by username_3 on 2018-12-31. Score: 1
  
  Can you check this PR
  
  <https://github.com/civicrm/civicrm-core/pull/13374>
  
  There seems to be a bug that allows you to change the payment schedule and wiping out the contributions in the process. The above patch will fix the same.
  
  
  ---
  
  