Answers.Body: <p>We finally poked around and noticed standard option groups with integer values did not use zero. We had used value zero to represent "No". We changed "No" to value 3 and updated the existing records. Once all zeroes were gone, the warning disappeared. Later, we noticed that other radio button option groups use Alphanumeric data type even if the values are integers. Ours had been configured as an Integer (INT11 in the database). I can't say whether either of these conditions are the root of the warning, but avoiding zero appears to have worked. See also:</p>
  
  <p><a href="https://civicrm.stackexchange.com/questions/18528/option-values-with-problematic-values/20462#20462">Option Values with problematic Values</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-18T17:57:35.940Z
Answers.LastActivityDate: 2017-09-18T17:57:35.940Z
Answers.UserDisplayName: Mark Westergaard
Body: <p>I'm getting this System Status notice:</p>
  
  <pre><code>The Following Option Values contain value fields that do not match the Data Type of the Option Group
  </code></pre>
  
  <p>It references an option group with 0 as one of the values. The group is used for a custom field of type Number. I went into the mysql database and saw that the option group had type String, so I changed that to Integer, also tried Float - nothing got rid of the error.</p>
  
  <p>Is it a spurious error due to a bug or am I not understanding something about how option groups and values work?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-12-08T22:29:35.143Z
Comments.Text: I've seen the same thing, plus now I have a complaint about a custom radio button field. It's ironic/amusing/or a bug that Civi is complaining about something that it was quite happy for me to do through the UI.
Comments.UserDisplayName: Andy Clark
Tags: <custom-fields><option>
Title: System status notice about option value 0 in number field
ThreadText: # System status notice about option value 0 in number field
  
  (Asked by: username_0 on 2016-12-08)
  
  I'm getting this System Status notice:
  
  ```
  The Following Option Values contain value fields that do not match the Data Type of the Option Group
  
  ```
  
  It references an option group with 0 as one of the values. The group is used for a custom field of type Number. I went into the mysql database and saw that the option group had type String, so I changed that to Integer, also tried Float - nothing got rid of the error.
  
  Is it a spurious error due to a bug or am I not understanding something about how option groups and values work?
  
  **Tags:** custom-fields, option
  
  > **Comments:**
  > **username_1**: I've seen the same thing, plus now I have a complaint about a custom radio button field. It's ironic/amusing/or a bug that Civi is complaining about something that it was quite happy for me to do through the UI.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2017-09-18. Score: 1
  
  We finally poked around and noticed standard option groups with integer values did not use zero. We had used value zero to represent "No". We changed "No" to value 3 and updated the existing records. Once all zeroes were gone, the warning disappeared. Later, we noticed that other radio button option groups use Alphanumeric data type even if the values are integers. Ours had been configured as an Integer (INT11 in the database). I can't say whether either of these conditions are the root of the warning, but avoiding zero appears to have worked. See also:
  
  [Option Values with problematic Values](https://civicrm.stackexchange.com/questions/18528/option-values-with-problematic-values/20462#20462)
  
  
  ---
  
  