Answers.Body: <p>Unfortunately, "disabled" controls both availability for entering data as well as for visibility on reports.</p>
  
  <p>If you disable field options, the data IS preserved - but will only be available for reporting/export if you (temporarily) re-enable the options.</p>
  
  <p>If this is completely unworkable in your scenario, you can try more advanced solutions for disabling items, such as Kboy's suggestion to hide unused fields with CSS, or running a SQL query directly against the database to pick up disabled options.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-01-15T15:52:57.830Z
Answers.Text: Thanks everyone, I have my answer. What I don't know is how to stop following an item.
Answers.UserDisplayName: EndAbuse Tech Coordinator
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-01-09T22:26:06.023Z
Answers.LastActivityDate: 2016-01-09T22:26:06.023Z
Answers.UserDisplayName: Jon G - Megaphone Tech
Answers.Body: <p>You might consider using css to hide the fields not in used, in this case you can still have them available for reporting, </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-01-08T21:49:47.727Z
Answers.LastActivityDate: 2016-01-08T21:49:47.727Z
Answers.UserDisplayName: Kboy
Body: <p>I'd like to disable some custom field fields, because we no longer want users to enter that data. But then I can no longer see the field in report filters. Is there another way I can get that data out without re-enabling the field?</p>
  
  <p>I would also like to disable some field options. Is the data preserved? Assuming so (maybe I shouldn't) how can I report or export it after it's disabled?</p>
  
  <p>Thanks everyone</p>
  
  <p>Thanks for the suggestions - however, I'm new to CiviCRM, what is CSS?  I think being able to change the visibility in the field when inputting would help, but you'd still have to have it visible for reporting.  (Other systems I have used just have a 'selectable' option tick box for each entry in the pick list - but this only controls new choices in a pick list, as all options are available for reporting.)</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-01-12T23:30:40.760Z
Comments.Text: is there any pointing asking where/how people are entering this data? if they are custom fields, but not in profiles, then are you giving users access to civicrm directly? asking in case this is more an issue of restricting what data users should/could update
Comments.UserDisplayName: petednz - fuzion
Tags: <custom-fields><civireport><export>
Title: Can I report data from a disabled custom field or option?
ThreadText: # Can I report data from a disabled custom field or option?
  
  (Asked by: username_0 on 2016-01-08)
  
  I'd like to disable some custom field fields, because we no longer want users to enter that data. But then I can no longer see the field in report filters. Is there another way I can get that data out without re-enabling the field?
  
  I would also like to disable some field options. Is the data preserved? Assuming so (maybe I shouldn't) how can I report or export it after it's disabled?
  
  Thanks everyone
  
  Thanks for the suggestions - however, I'm new to CiviCRM, what is CSS? I think being able to change the visibility in the field when inputting would help, but you'd still have to have it visible for reporting. (Other systems I have used just have a 'selectable' option tick box for each entry in the pick list - but this only controls new choices in a pick list, as all options are available for reporting.)
  
  **Tags:** custom-fields, civireport, export
  
  > **Comments:**
  > **username_1**: is there any pointing asking where/how people are entering this data? if they are custom fields, but not in profiles, then are you giving users access to civicrm directly? asking in case this is more an issue of restricting what data users should/could update  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_3 on 2016-01-08. Score: 3 | Accepted answer
  
  You might consider using css to hide the fields not in used, in this case you can still have them available for reporting,
  
  
  ---
  
  ### Answer by username_2 on 2016-01-09. Score: 2
  
  Unfortunately, "disabled" controls both availability for entering data as well as for visibility on reports.
  
  If you disable field options, the data IS preserved - but will only be available for reporting/export if you (temporarily) re-enable the options.
  
  If this is completely unworkable in your scenario, you can try more advanced solutions for disabling items, such as username_3's suggestion to hide unused fields with CSS, or running a SQL query directly against the database to pick up disabled options.
  
  > **Comments:**
  > **username_0**: Thanks everyone, I have my answer. What I don't know is how to stop following an item.  
  
  ---
  
  