Answers.Body: <p>That sounds familiar, I recall some issues similar to what you are reporting (i.e. that message coming up in a misleading way).</p>
  
  <p>I'd try upgrading to a more recent 4.6.x to see if that fixes it (you're going to want to do that for security reasons in any case). The 4.6.x series is reasonably stable, there isn't usually any reason not to upgrade.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-02T14:05:00.087Z
Answers.LastActivityDate: 2017-05-02T14:05:00.087Z
Answers.UserDisplayName: Alan Dixon
Body: <p>I am trying to add event participants back end through Events->Register Event participants. I am getting this error, </p>
  
  <p>"Profile search, view and edit are not supported for Profiles which include fields for more than one record type." Civicrm version 4.6.8.</p>
  
  <p>There are two profile fields configured in the event with fields of type 'individual' and 'contact'.</p>
  
  <p>Any help can be appreciated. Thanks in advance.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-05-02T11:28:06.407Z
Comments.Text: Could you share more information on the fields you are using? E.g. post a screenshot of the profile?
Comments.UserDisplayName: Fabian
Tags: <civievent><profile><registration>
Title: Unable to add Event Participants backend
ThreadText: # Unable to add Event Participants backend
  
  (Asked by: username_0 on 2017-05-02)
  
  I am trying to add event participants back end through Events->Register Event participants. I am getting this error,
  
  "Profile search, view and edit are not supported for Profiles which include fields for more than one record type." Civicrm version 4.6.8.
  
  There are two profile fields configured in the event with fields of type 'individual' and 'contact'.
  
  Any help can be appreciated. Thanks in advance.
  
  **Tags:** civievent, profile, registration
  
  > **Comments:**
  > **username_1**: Could you share more information on the fields you are using? E.g. post a screenshot of the profile?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2017-05-02. Score: 1
  
  That sounds familiar, I recall some issues similar to what you are reporting (i.e. that message coming up in a misleading way).
  
  I'd try upgrading to a more recent 4.6.x to see if that fixes it (you're going to want to do that for security reasons in any case). The 4.6.x series is reasonably stable, there isn't usually any reason not to upgrade.
  
  
  ---
  
  