Answers.Body: <p>I was able to replicate this issue.</p>
  
  <p>Historically, CiviCRM didn't support multiple payments on a single contribution.  So the check number is part of the contribution.  However, now that it supports multiple payments, the check number is part of the financial transaction.</p>
  
  <p>The check number being searched is the contribution's, not the financial transaction's.  I think it needs to be changed; I can't think of a case where it's desirable not to.</p>
  
  <p>I just opened a ticket on <a href="https://lab.civicrm.org" rel="nofollow noreferrer">https://lab.civicrm.org</a>, <a href="https://lab.civicrm.org/dev/financial/issues/37" rel="nofollow noreferrer">financial#37</a>.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-01-10T16:15:14.923Z
Answers.Text: Do you have a suggestion that would solve this problem in the short term? I am sure there are others with this problem that maybe don't know it is an issue.
Answers.UserDisplayName: WVMike
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-01-10T16:21:24.917Z
Answers.Text: Afraid not, @WVMike.  It needs someone to look at it. Is your organization in a position to fund the fix?  As we like to say, CiviCRM is free to use, but not to write :)  If there was funding, I'm sure someone could get on it quite quickly, I don't think it's a ton of work to resolve.
Answers.UserDisplayName: Jon G - Megaphone Tech
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-01-16T14:32:37.070Z
Answers.Text: Having same problem after the upgrade
Answers.UserDisplayName: Hassan Farooq
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-01-16T16:04:24.313Z
Answers.Text: @HassanFarooq I opened a ticket, but unless someone devotes resources to fixing it (code or money) it's probably going to remain that way.
Answers.UserDisplayName: Jon G - Megaphone Tech
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-01-09T16:49:58.850Z
Answers.LastActivityDate: 2019-01-09T16:56:08.953Z
Answers.LastEditDate: 2019-01-09T16:56:08.953Z
Answers.UserDisplayName: Jon G - Megaphone Tech
Body: <p>I recently upgraded to 5.5.0 and now when you edit a pending pay later contribution, add a check number, change status to complete and then i go to search contributions, enter the payment method and search by check number i get no result.</p>
  
  <p>I  </p>
  
Tags: <civicontribute>
Title: Searching by check number after upgrading to 5.5.0
ThreadText: # Searching by check number after upgrading to 5.5.0
  
  (Asked by: username_0 on 2019-01-09)
  
  I recently upgraded to 5.5.0 and now when you edit a pending pay later contribution, add a check number, change status to complete and then i go to search contributions, enter the payment method and search by check number i get no result.
  
  I
  
  **Tags:** civicontribute
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-01-09. Score: 3
  
  I was able to replicate this issue.
  
  Historically, CiviCRM didn't support multiple payments on a single contribution. So the check number is part of the contribution. However, now that it supports multiple payments, the check number is part of the financial transaction.
  
  The check number being searched is the contribution's, not the financial transaction's. I think it needs to be changed; I can't think of a case where it's desirable not to.
  
  I just opened a ticket on <https://lab.civicrm.org>, [financial#37](https://lab.civicrm.org/dev/financial/issues/37).
  
  > **Comments:**
  > **username_0**: Do you have a suggestion that would solve this problem in the short term? I am sure there are others with this problem that maybe don't know it is an issue.  
  > **username_1**: Afraid not, @username_0.  It needs someone to look at it. Is your organization in a position to fund the fix?  As we like to say, CiviCRM is free to use, but not to write :)  If there was funding, I'm sure someone could get on it quite quickly, I don't think it's a ton of work to resolve.  
  > **username_2**: Having same problem after the upgrade  
  > **username_1**: @HassanFarooq I opened a ticket, but unless someone devotes resources to fixing it (code or money) it's probably going to remain that way.  
  
  ---
  
  