Answers.Body: <p>I solved this by looking in the civicrm_price_field table and noticed that the missing price field had an expiry date of '000-00-00 00:00:00' vs. NULL for other expiry dates. Setting the price field expiry to NULL allowed the price field to be redisplayed.</p>
  <p>On the configuration screen, those two values both appear the same.</p>
  <p>Conclusion: a '0000-00-00 00:00:00' in a price field row expiry field should be considered invalid/error.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-10-08T01:38:03.073Z
Answers.Text: We just found that similar happened. User remove an 'old' Expiry Date (according to the logs) and bingo it broked. will push a PR today hopefully
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-10-08T21:56:25.550Z
Answers.Text: ok. more specifically the problem can be caused by having a price field with an expire Date/Time, and then removing the Date by clicking in to it, rather than using the X - therefore leaving the Time behind eg as 00:00 - which i guess puts it pretty close to the Big Bang :-)
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-10-08T21:56:56.163Z
Answers.Text: am suggesting that if a fix is hard, then at least a warning on Submit if date is empty but Time is not
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-10-09T20:49:49.147Z
Answers.Text: 0000-00-00 00:00:00 wouldn't be the big bang, more like year 0 CE.
Answers.UserDisplayName: Alan Dixon
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-10-09T20:50:54.147Z
Answers.Text: A warning on submit wouldn't deal with old bad data, we'd need one of those system check thingys to warn about that also.
Answers.UserDisplayName: Alan Dixon
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-08-31T16:16:24.517Z
Answers.LastActivityDate: 2020-08-31T16:16:24.517Z
Answers.UserDisplayName: Alan Dixon
Body: <p>After a recent civicrm upgrade, one of my pricefields in a price set just 'disappeared'. There were no errors showing and the pricefield appeared to be correctly configured.</p>
  
Tags: <civicontribute><price-sets>
Title: Where did my price field go? It's missing!
ThreadText: # Where did my price field go? It's missing!
  
  (Asked by: username_0 on 2020-08-31)
  
  After a recent civicrm upgrade, one of my pricefields in a price set just 'disappeared'. There were no errors showing and the pricefield appeared to be correctly configured.
  
  **Tags:** civicontribute, price-sets
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2020-08-31. Score: 3
  
  I solved this by looking in the civicrm\_price\_field table and noticed that the missing price field had an expiry date of '000-00-00 00:00:00' vs. NULL for other expiry dates. Setting the price field expiry to NULL allowed the price field to be redisplayed.
  
  On the configuration screen, those two values both appear the same.
  
  Conclusion: a '0000-00-00 00:00:00' in a price field row expiry field should be considered invalid/error.
  
  > **Comments:**
  > **username_1**: We just found that similar happened. User remove an 'old' Expiry Date (according to the logs) and bingo it broked. will push a PR today hopefully  
  > **username_1**: ok. more specifically the problem can be caused by having a price field with an expire Date/Time, and then removing the Date by clicking in to it, rather than using the X - therefore leaving the Time behind eg as 00:00 - which i guess puts it pretty close to the Big Bang :-)  
  > **username_1**: am suggesting that if a fix is hard, then at least a warning on Submit if date is empty but Time is not  
  > **username_0**: 0000-00-00 00:00:00 wouldn't be the big bang, more like year 0 CE.  
  > **username_0**: A warning on submit wouldn't deal with old bad data, we'd need one of those system check thingys to warn about that also.  
  
  ---
  
  