Answers.Body: <p>This warning appears when the content column type of the current selected field is different than the new one -> you'll lose all the information that is currently stored.</p>
  
  <p>For example: changing from number to text won't be a huge problem but changing from text to date will result in a data loss </p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-06-14T09:28:25.367Z
Answers.Text: DO you mean its just information or that there is something wrong? In the middle of a build I don't want to be frightened that the database is going to be 'corrupted' . Its not clear from the UX of this if any action is required
Answers.UserDisplayName: joomkit
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-06-14T10:06:30.420Z
Answers.Text: It's just an information. When you change the type you'll lose data
Answers.UserDisplayName: Robin Schambach
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-06-13T16:35:41.427Z
Answers.LastActivityDate: 2018-06-13T16:35:41.427Z
Answers.UserDisplayName: Robin Schambach
Body: <p>I am seeing warning icons on drop down fields like this
  <a href="https://i.sstatic.net/KvtsC.jpg" rel="nofollow noreferrer"><img src="https://i.sstatic.net/KvtsC.jpg" alt="Drop down with warnings"></a></p>
  
  <p>Where does this come from?</p>
  
Tags: <fieldtypes>
Title: warning icon on fields
ThreadText: # warning icon on fields
  
  (Asked by: username_0 on 2018-06-13)
  
  I am seeing warning icons on drop down fields like this
  [![Drop down with warnings](https://i.sstatic.net/KvtsC.jpg)](https://i.sstatic.net/KvtsC.jpg)
  
  Where does this come from?
  
  **Tags:** fieldtypes
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2018-06-13. Score: 4 | Accepted answer
  
  This warning appears when the content column type of the current selected field is different than the new one -> you'll lose all the information that is currently stored.
  
  For example: changing from number to text won't be a huge problem but changing from text to date will result in a data loss
  
  > **Comments:**
  > **username_0**: DO you mean its just information or that there is something wrong? In the middle of a build I don't want to be frightened that the database is going to be 'corrupted' . Its not clear from the UX of this if any action is required  
  > **username_1**: It's just an information. When you change the type you'll lose data  
  
  ---
  
  