Answers.Body: <p>You can disable the codes and then sort by what is still active. I also recommend coming up with a naming convention that makes it easier to sort.</p>
  
  <p>You could also set up an automatic discount for certain memberships per certain events, which would cut down on the need for so many codes. </p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-08-06T23:26:19.857Z
Answers.Text: What version are you seeing a sort by active on?  I don't see it on my installation. Also, personally, I think relying on "naming strategy" is a workaround, but the tool itself could/should allow for filters/etc. like a Drupal view.....perhaps I can code this or sponsor some change.
Answers.UserDisplayName: Zachary
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-08-07T05:40:49.180Z
Answers.Text: Drupal, civicrm 5.3.1 and cividiscount 3.4. A filter isn't a bad idea. But disabling old codes is a good idea too.
Answers.UserDisplayName: Christia
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-08-07T17:04:52.010Z
Answers.Text: I'm still on 3.2 cividiscount. There are a couple bugs on the github that would prevent me from updating right now
Answers.UserDisplayName: Zachary
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-08-07T18:12:57.430Z
Answers.Text: I use GIT also and I created a separate repository for my CiviCRM extensions, since they are in the files directory, which is normally ignored. It made my life much easier.
Answers.UserDisplayName: Christia
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-08-06T22:00:28.193Z
Answers.LastActivityDate: 2018-08-07T05:42:03.397Z
Answers.LastEditDate: 2018-08-07T05:42:03.397Z
Answers.UserDisplayName: Christia
Body: <p>How do you manage a long list (100+) of CiviDiscount codes?</p>
  
  <p>We hold an annual conference and make about 70 codes per conference - so the list adds up. </p>
  
  <p><a href="https://civicrm.stackexchange.com/questions/20508/can-i-remove-old-discount-codes-without-affecting-contribution-records">Can I remove old discount codes without affecting contribution records?</a> seems to be possible, although deleting them seems to be not the best practice?</p>
  
  <p>Ideas:</p>
  
  <p>How difficult would it be to implement a quick filter at the top that toggles the view to show active and inactive (or both) codes?</p>
  
  <p>Or, what about a quick filter for 'Event' the codes are attached to? (or something like that?)</p>
  
  <p>Alternatively - could a Drupal view handle this? Thanks!</p>
  
Tags: <cividiscount>
Title: Long List of CiviDiscount Codes Needs Management
ThreadText: # Long List of CiviDiscount Codes Needs Management
  
  (Asked by: username_0 on 2018-08-06)
  
  How do you manage a long list (100+) of CiviDiscount codes?
  
  We hold an annual conference and make about 70 codes per conference - so the list adds up.
  
  [Can I remove old discount codes without affecting contribution records?](https://civicrm.stackexchange.com/questions/20508/can-i-remove-old-discount-codes-without-affecting-contribution-records) seems to be possible, although deleting them seems to be not the best practice?
  
  Ideas:
  
  How difficult would it be to implement a quick filter at the top that toggles the view to show active and inactive (or both) codes?
  
  Or, what about a quick filter for 'Event' the codes are attached to? (or something like that?)
  
  Alternatively - could a Drupal view handle this? Thanks!
  
  **Tags:** cividiscount
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2018-08-06. Score: 0 | Accepted answer
  
  You can disable the codes and then sort by what is still active. I also recommend coming up with a naming convention that makes it easier to sort.
  
  You could also set up an automatic discount for certain memberships per certain events, which would cut down on the need for so many codes.
  
  > **Comments:**
  > **username_0**: What version are you seeing a sort by active on?  I don't see it on my installation. Also, personally, I think relying on "naming strategy" is a workaround, but the tool itself could/should allow for filters/etc. like a Drupal view.....perhaps I can code this or sponsor some change.  
  > **username_1**: Drupal, civicrm 5.3.1 and cividiscount 3.4. A filter isn't a bad idea. But disabling old codes is a good idea too.  
  > **username_0**: I'm still on 3.2 cividiscount. There are a couple bugs on the github that would prevent me from updating right now  
  > **username_1**: I use GIT also and I created a separate repository for my CiviCRM extensions, since they are in the files directory, which is normally ignored. It made my life much easier.  
  
  ---
  
  