Answers.Body: <p>Disabling of price field is actually helpful in case you need it in future and it is not shown anywhere else except price field browse page.</p>
  
  <p>Eg:</p>
  
  <ul>
  <li><p>Configure an event with regular priceset(is_quick_config = 1) with three field options.</p></li>
  <li><p>Remove two of them (backend - civi disables it).</p></li>
  <li><p>Now, a user creates a new priceset from <code>Manage Price Set</code> page and configure on this event. At this point, your regular priceset is not lost. Its value of <code>is_quick_config</code> is changed to zero, hence it will be now shown on the list of PriceSet page.</p></li>
  </ul>
  
  <p>So, it provides a flexibility of again choosing the original priceset for your event. You can also delete unwanted field options of it from <code>civicrm/admin/price/field/option?action=browse&amp;reset=1&amp;sid={set_id}&amp;fid={field_id}</code> just like normal pricesets, if it is not used by any other event.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-08-10T18:05:59.653Z
Answers.Text: what about if a user has already registered using the now disabled amount, would that be another reason to keep the value in the db?
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-08-12T14:29:04.367Z
Answers.Text: Yea, agree to that. as it isn't allowed to delete priceset/field if it is being used by any contribution row as per https://civicrm.stackexchange.com/questions/19721/unable-to-delete-price-field-from-price-set-used-for-contributions/19722#19722
Answers.UserDisplayName: jitendra - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-12T09:54:19.957Z
Answers.LastActivityDate: 2017-05-12T12:24:12.617Z
Answers.LastEditDate: 2017-05-12T12:24:12.617Z
Answers.UserDisplayName: jitendra - fuzion
Body: <p>If I set up an event and use the regular fees section rather than setting up a price set then it stores this information in a price set.
  <a href="https://i.sstatic.net/9xEUx.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/9xEUx.png" alt="Event regular fees page"></a>
  If I remove a value from this table then it stays in the database. If I know the price set id then I can find these fields via the UI
  <a href="https://i.sstatic.net/K2M1X.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/K2M1X.png" alt="Price options"></a>
  Why does the system keep this other value?
  Having these other fields causes confusion when creating views because as far as a basic user can tell there is only one fee and there is no reason for them to expect there to be other ones hiding.</p>
  
Tags: <civievent><price-sets>
Title: Why if you remove a regular fee from the list on an event does it not get removed from the price set in the database?
ThreadText: # Why if you remove a regular fee from the list on an event does it not get removed from the price set in the database?
  
  (Asked by: username_0 on 2017-05-12)
  
  If I set up an event and use the regular fees section rather than setting up a price set then it stores this information in a price set.
  [![Event regular fees page](https://i.sstatic.net/9xEUx.png)](https://i.sstatic.net/9xEUx.png)
  If I remove a value from this table then it stays in the database. If I know the price set id then I can find these fields via the UI
  [![Price options](https://i.sstatic.net/K2M1X.png)](https://i.sstatic.net/K2M1X.png)
  Why does the system keep this other value?
  Having these other fields causes confusion when creating views because as far as a basic user can tell there is only one fee and there is no reason for them to expect there to be other ones hiding.
  
  **Tags:** civievent, price-sets
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2017-05-12. Score: 1
  
  Disabling of price field is actually helpful in case you need it in future and it is not shown anywhere else except price field browse page.
  
  Eg:
  
  * Configure an event with regular priceset(is\_quick\_config = 1) with three field options.
  * Remove two of them (backend - civi disables it).
  * Now, a user creates a new priceset from `Manage Price Set` page and configure on this event. At this point, your regular priceset is not lost. Its value of `is_quick_config` is changed to zero, hence it will be now shown on the list of PriceSet page.
  
  So, it provides a flexibility of again choosing the original priceset for your event. You can also delete unwanted field options of it from `civicrm/admin/price/field/option?action=browse&reset=1&sid={set_id}&fid={field_id}` just like normal pricesets, if it is not used by any other event.
  
  > **Comments:**
  > **username_2**: what about if a user has already registered using the now disabled amount, would that be another reason to keep the value in the db?  
  > **username_1**: Yea, agree to that. as it isn't allowed to delete priceset/field if it is being used by any contribution row as per https://civicrm.stackexchange.com/questions/19721/unable-to-delete-price-field-from-price-set-used-for-contributions/19722#19722  
  
  ---
  
  