Answers.Body: <p>I suspect the OP needs to avoid the creation of double backend membership with the same type. Something which would look like -</p>
  
  <p><a href="https://i.sstatic.net/720k6.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/720k6.png" alt="enter image description here"></a></p>
  
  <p>This could be a bug(not sure) as this doesn't happen when registered through contribution pages. I don't think there is any setting in civi UI which would avoid this, but it is possible with a small extension(<a href="https://docs.civicrm.org/dev/en/master/extensions/civix/" rel="nofollow noreferrer">learn here</a>) where you need to check for double membership type registering for a single contact id.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-09-24T11:20:28.030Z
Answers.Text: There might be legitimate reasons for having duplicate memberships on some sites so we should not put such a restriction in core.  But I would think this could easily be enforced by writing a simple extension.
Answers.UserDisplayName: Matthew Wire
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-25T14:14:34.500Z
Answers.LastActivityDate: 2017-03-25T14:14:34.500Z
Answers.UserDisplayName: jitendra - fuzion
Answers.Body: <p>It sounds to me like a staff training issue rather than a software issue. The way you describe the problem, your staff are going to create a new membership, then when a big warning box pops up telling them that it already exists, they ignore it and carry on anyway.</p>
  
  <p>If staff training doesn't solve the problem (e.g. you are using a revolving door of volunteers and there is no way to train them) then you probably shouldn't be giving them access to your CRM at all. Instead, you could set some Webforms to let them enter data for you without the power to create duplicate memberships.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-09-24T20:04:46.683Z
Answers.LastActivityDate: 2018-09-24T20:04:46.683Z
Answers.UserDisplayName: Coleman
Body: <p>When I connect a contact to same membership type, the system displays a warning message that it is a duplicate membership for the same contact, but still allows to to perform the action. Then I get two active records for the contact with same membership. How can I avoid it in such way that the system will block the ability to create more that one active record for same membership type?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-03-23T11:14:02.057Z
Comments.Text: Marina - you probably need to explain your workflow precisely as this sounds uncommon if you use the normal civimember approach. why do you want a contact to have more than one membership. are you trying to 'renew' them but not using the 'renew' feature? or something else?
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-03-23T12:41:10.947Z
Comments.Text: I would like to avoid such situation in order to prevent from creating invalid data by user
Comments.UserDisplayName: Marina
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-03-23T20:17:31.707Z
Comments.Text: Sorry. I would like to help and am sure others would too, but you have not provided enough information. Start from the beginning. A person signs up through a Contribution page to join? Yes or No. Or do you join them at the backend. Then what? Do you want to renew them? Or do you want to give them a second membership? if the latter why? etc etc
Comments.UserDisplayName: petednz - fuzion
Tags: <civimember>
Title: How to avoid a duplicate membership for same contact
ThreadText: # How to avoid a duplicate membership for same contact
  
  (Asked by: username_0 on 2017-03-23)
  
  When I connect a contact to same membership type, the system displays a warning message that it is a duplicate membership for the same contact, but still allows to to perform the action. Then I get two active records for the contact with same membership. How can I avoid it in such way that the system will block the ability to create more that one active record for same membership type?
  
  **Tags:** civimember
  
  > **Comments:**
  > **username_1**: username_0 - you probably need to explain your workflow precisely as this sounds uncommon if you use the normal civimember approach. why do you want a contact to have more than one membership. are you trying to 'renew' them but not using the 'renew' feature? or something else?  
  > **username_0**: I would like to avoid such situation in order to prevent from creating invalid data by user  
  > **username_1**: Sorry. I would like to help and am sure others would too, but you have not provided enough information. Start from the beginning. A person signs up through a Contribution page to join? Yes or No. Or do you join them at the backend. Then what? Do you want to renew them? Or do you want to give them a second membership? if the latter why? etc etc  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2017-03-25. Score: 3
  
  I suspect the OP needs to avoid the creation of double backend membership with the same type. Something which would look like -
  
  [![enter image description here](https://i.sstatic.net/720k6.png)](https://i.sstatic.net/720k6.png)
  
  This could be a bug(not sure) as this doesn't happen when registered through contribution pages. I don't think there is any setting in civi UI which would avoid this, but it is possible with a small extension([learn here](https://docs.civicrm.org/dev/en/master/extensions/civix/)) where you need to check for double membership type registering for a single contact id.
  
  > **Comments:**
  > **username_3**: There might be legitimate reasons for having duplicate memberships on some sites so we should not put such a restriction in core.  But I would think this could easily be enforced by writing a simple extension.  
  
  ---
  
  ### Answer by username_4 on 2018-09-24. Score: 1
  
  It sounds to me like a staff training issue rather than a software issue. The way you describe the problem, your staff are going to create a new membership, then when a big warning box pops up telling them that it already exists, they ignore it and carry on anyway.
  
  If staff training doesn't solve the problem (e.g. you are using a revolving door of volunteers and there is no way to train them) then you probably shouldn't be giving them access to your CRM at all. Instead, you could set some Webforms to let them enter data for you without the power to create duplicate memberships.
  
  
  ---
  
  