Answers.Body: <p>Ah, you have the answer in your question. If you look at your reference to the current code, it should be recognizing that MysqlColumnNameOrAlias instead of generating the error in the default clause of the switch.</p>
  
  <p>So I checked the history of that file, and the MysqlColumnNameOrAlias case was only added mid-last year.</p>
  
  <p>Conclusion - upgrade your Civi to the latest 4.6 (which you should do anyway because of security reasons).</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-01-23T09:17:50.977Z
Answers.Text: Ah that makes sense as I thought it was handled by that code. We're looking to upgrade to 4.7 soon so that will resolve. Thanks to you and everyone else who responded!
Answers.UserDisplayName: Lawrence Welsby
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-01-17T17:50:28.753Z
Answers.LastActivityDate: 2017-01-17T17:50:28.753Z
Answers.UserDisplayName: Alan Dixon
Body: <p>We're on 4.6.8 and having an issue where when saving an activity which is assigned to a contact the following error is displayed:</p>
  <blockquote>
  <p>Sorry but we are not able to provide this at the moment.</p>
  <p>Sorry an Error Occured
  MysqlColumnNameOrAlias is not a recognised (camel cased) data type.</p>
  </blockquote>
  <p>If it is not assigned to anyone there is no error. However, if you click back and go into the record again the activity has in fact been saved. Not a massive issue as the activity is saved but it's not good from a usability perspective.</p>
  <p>From looking online it looks like the following code is where the error is being generated from:</p>
  <p><a href="https://github.com/civicrm/civicrm-core/blob/master/CRM/Utils/Type.php" rel="nofollow noreferrer">https://github.com/civicrm/civicrm-core/blob/master/CRM/Utils/Type.php</a></p>
  <p>Any ideas what is causing this?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-01-13T12:09:38.480Z
Comments.Text: This is a good question!  To solve your problem, we'll need to see the expanded debugging information.  In CiviCRM, please go to **Administer menu > System Settings > Debugging and Error Handling**, select "Yes" to both "Enable Debugging" and "Display Backtrace", and press "Save".  Repeat the problem that caused your error, and you'll see much a much more detailed error.  Please update this question with the expanded error and backtrace - and don't forget to disable debugging/backtrace when you're done!
Comments.UserDisplayName: Jon G - Megaphone Tech
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-01-13T12:40:58.927Z
Comments.Text: could you double check on your CRM/Utils/Type.php if the  MysqlColumnNameOrAlias is there too?
Comments.UserDisplayName: Xavier
Tags: <error><activity>
Title: Error when assigning Activity to a contact
ThreadText: # Error when assigning Activity to a contact
  
  (Asked by: username_0 on 2017-01-13)
  
  We're on 4.6.8 and having an issue where when saving an activity which is assigned to a contact the following error is displayed:
  
  > Sorry but we are not able to provide this at the moment.
  >
  > Sorry an Error Occured
  > MysqlColumnNameOrAlias is not a recognised (camel cased) data type.
  
  If it is not assigned to anyone there is no error. However, if you click back and go into the record again the activity has in fact been saved. Not a massive issue as the activity is saved but it's not good from a usability perspective.
  
  From looking online it looks like the following code is where the error is being generated from:
  
  <https://github.com/civicrm/civicrm-core/blob/master/CRM/Utils/Type.php>
  
  Any ideas what is causing this?
  
  **Tags:** error, activity
  
  > **Comments:**
  > **username_1**: This is a good question!  To solve your problem, we'll need to see the expanded debugging information.  In CiviCRM, please go to **Administer menu > System Settings > Debugging and Error Handling**, select "Yes" to both "Enable Debugging" and "Display Backtrace", and press "Save".  Repeat the problem that caused your error, and you'll see much a much more detailed error.  Please update this question with the expanded error and backtrace - and don't forget to disable debugging/backtrace when you're done!  
  > **username_2**: could you double check on your CRM/Utils/Type.php if the  MysqlColumnNameOrAlias is there too?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_3 on 2017-01-17. Score: 1 | Accepted answer
  
  Ah, you have the answer in your question. If you look at your reference to the current code, it should be recognizing that MysqlColumnNameOrAlias instead of generating the error in the default clause of the switch.
  
  So I checked the history of that file, and the MysqlColumnNameOrAlias case was only added mid-last year.
  
  Conclusion - upgrade your Civi to the latest 4.6 (which you should do anyway because of security reasons).
  
  > **Comments:**
  > **username_0**: Ah that makes sense as I thought it was handled by that code. We're looking to upgrade to 4.7 soon so that will resolve. Thanks to you and everyone else who responded!  
  
  ---
  
  