Answers.Body: <p>As I understand you correctly, you were exploiting a bug, and now its is fixed you search for another solution. One option is to undo the bugfix.</p>
  
  <p>You can do this with the following actions:</p>
  
  <ul>
  <li>Lookup the issue (CRM-19550).</li>
  <li>Find the pull that contains the patch (<a href="https://github.com/civicrm/civicrm-core/pull/9303" rel="nofollow noreferrer">https://github.com/civicrm/civicrm-core/pull/9303</a>).</li>
  <li>Create a patch file</li>
  </ul>
  
  <p><code>wget <a href="https://github.com/civicrm/civicrm-core/pull/9303.patch" rel="nofollow noreferrer">https://github.com/civicrm/civicrm-core/pull/9303.patch</a> > CRM19550.patch</code></p>
  
  <ul>
  <li>Reverse apply the patch on your 4.7.14 installation</li>
  </ul>
  
  <p><code>git apply -R CRM19550.patch</code> in the <code>[civicrm.root]</code>.</p>
  
  <p>You have to follow the same procedure with every upgrade.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-01-13T11:21:02.950Z
Answers.Text: Yeah, that does look like my only option :\ At least it's only one file!
Answers.UserDisplayName: liblogger
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-01-17T11:56:31.973Z
Answers.Text: (Finally got a chance to test this and it seems to be working okay)
Answers.UserDisplayName: liblogger
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-01-12T13:42:19.327Z
Answers.LastActivityDate: 2017-01-12T13:42:19.327Z
Answers.UserDisplayName: Kainuk - CiviCooP
Answers.Body: <p>Perhaps you could do this via a non-Civi webform accessible only to your data entry volunteers (use webform if you are using Drupal as your CMS, or one of the forms plugins that are available for Wordpress) and not collect it in CiviCRM at all. Given that CiviCRM is all about linking data to named contacts and you expressly don't want to do this, then using Civi for it seems to be going against the grain.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-01-15T15:37:21.367Z
Answers.Text: We also collect non-anonymous feedback (among other things), and find that having the data in one place, connected to information about events and so on, is more useful to us.
Answers.UserDisplayName: liblogger
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-01-13T16:27:49.723Z
Answers.LastActivityDate: 2017-01-13T16:27:49.723Z
Answers.UserDisplayName: Graham
Body: <p>We use CiviCRM to collect anonymous feedback and equal opps data from event attendees in custom fields connected to an event participant role, and to avoid having to create multiple anonymous individual contact records, we have been registering multiple participant instances for a single anonymous record. Unfortunately, following the latest update to 4.7.14, this is no longer possible.</p>
  
  <p>I realise that we've been taking advantage of something many would consider a bug - I'm pretty sure this change is a result of this bugfix: <a href="https://issues.civicrm.org/jira/browse/CRM-19550" rel="nofollow noreferrer">https://issues.civicrm.org/jira/browse/CRM-19550</a> - but it makes our life vastly more complicated, because we'll have to create upwards of 100 anonymous records and anyone entering data will have to keep track of which participants have already been added (not a problem when there's 10 attendees; definitely a problem when there's 75).</p>
  
  <p>I'm also concerned that if we have to correct information in participant records that are already in the system, we won't be able to without re-assigning the participant contact record, or, worse, that the custom participant data will become conflated. </p>
  
  <p>Is there a way to disable/edit whatever dedupe rule is being used here? (I'm assuming that the participant records are still saved with a unique id and won't get overwritten - if this isn't case, I'd appreciate a heads up)</p>
  
  <p>I think this may be related to this issue: <a href="https://civicrm.stackexchange.com/questions/15826/enable-multiple-event-registration-for-same-purchaser-participant">Enable multiple event registration for same purchaser/participant</a> - however, that problem relates to individuals signing themselves up to events, not participants who are being registered by an administrator, and so the suggested fix doesn't apply here (even if it did, it would require us to enable online registration, which we definitely don't want!)</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-01-12T13:41:05.800Z
Comments.Text: I don't know the details of your use case, but maybe you could use access controls to limit who amongst your people can see/enter/edit this feedback and equal opps data, and thereby use real contact/participant records?
Comments.UserDisplayName: Graham
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-01-13T11:06:50.363Z
Comments.Text: @Graham - Unfortunately this isn't possible - quite apart from it being bad practice (We're a non-profit), all the data is collected anonymously, and we rely on volunteers for data entry.
Comments.UserDisplayName: liblogger
Tags: <civievent><registration><duplicate-contacts>
Title: Unable to add multiple participant registrations for one contact
ThreadText: # Unable to add multiple participant registrations for one contact
  
  (Asked by: username_0 on 2017-01-12)
  
  We use CiviCRM to collect anonymous feedback and equal opps data from event attendees in custom fields connected to an event participant role, and to avoid having to create multiple anonymous individual contact records, we have been registering multiple participant instances for a single anonymous record. Unfortunately, following the latest update to 4.7.14, this is no longer possible.
  
  I realise that we've been taking advantage of something many would consider a bug - I'm pretty sure this change is a result of this bugfix: <https://issues.civicrm.org/jira/browse/CRM-19550> - but it makes our life vastly more complicated, because we'll have to create upwards of 100 anonymous records and anyone entering data will have to keep track of which participants have already been added (not a problem when there's 10 attendees; definitely a problem when there's 75).
  
  I'm also concerned that if we have to correct information in participant records that are already in the system, we won't be able to without re-assigning the participant contact record, or, worse, that the custom participant data will become conflated.
  
  Is there a way to disable/edit whatever dedupe rule is being used here? (I'm assuming that the participant records are still saved with a unique id and won't get overwritten - if this isn't case, I'd appreciate a heads up)
  
  I think this may be related to this issue: [Enable multiple event registration for same purchaser/participant](https://civicrm.stackexchange.com/questions/15826/enable-multiple-event-registration-for-same-purchaser-participant) - however, that problem relates to individuals signing themselves up to events, not participants who are being registered by an administrator, and so the suggested fix doesn't apply here (even if it did, it would require us to enable online registration, which we definitely don't want!)
  
  **Tags:** civievent, registration, duplicate-contacts
  
  > **Comments:**
  > **username_1**: I don't know the details of your use case, but maybe you could use access controls to limit who amongst your people can see/enter/edit this feedback and equal opps data, and thereby use real contact/participant records?  
  > **username_0**: @username_1 - Unfortunately this isn't possible - quite apart from it being bad practice (We're a non-profit), all the data is collected anonymously, and we rely on volunteers for data entry.  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2017-01-12. Score: 1 | Accepted answer
  
  As I understand you correctly, you were exploiting a bug, and now its is fixed you search for another solution. One option is to undo the bugfix.
  
  You can do this with the following actions:
  
  * Lookup the issue (CRM-19550).
  * Find the pull that contains the patch (<https://github.com/civicrm/civicrm-core/pull/9303>).
  * Create a patch file
  
  `wget https://github.com/civicrm/civicrm-core/pull/9303.patch > CRM19550.patch`
  
  * Reverse apply the patch on your 4.7.14 installation
  
  `git apply -R CRM19550.patch` in the `[civicrm.root]`.
  
  You have to follow the same procedure with every upgrade.
  
  > **Comments:**
  > **username_0**: Yeah, that does look like my only option :\ At least it's only one file!  
  > **username_0**: (Finally got a chance to test this and it seems to be working okay)  
  
  ---
  
  ### Answer by username_1 on 2017-01-13. Score: 0
  
  Perhaps you could do this via a non-Civi webform accessible only to your data entry volunteers (use webform if you are using Drupal as your CMS, or one of the forms plugins that are available for Wordpress) and not collect it in CiviCRM at all. Given that CiviCRM is all about linking data to named contacts and you expressly don't want to do this, then using Civi for it seems to be going against the grain.
  
  > **Comments:**
  > **username_0**: We also collect non-anonymous feedback (among other things), and find that having the data in one place, connected to information about events and so on, is more useful to us.  
  
  ---
  
  