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?
3
-
2Marina - 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?– petednz - fuzion ♦Commented Mar 23, 2017 at 11:14
-
I would like to avoid such situation in order to prevent from creating invalid data by user– MarinaCommented Mar 23, 2017 at 12:41
-
2Sorry. 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– petednz - fuzion ♦Commented Mar 23, 2017 at 20:17
Add a comment
|
2 Answers
I suspect the OP needs to avoid the creation of double backend membership with the same type. Something which would look like -
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) where you need to check for double membership type registering for a single contact id.
answered Mar 25, 2017 at 14:14
-
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. Commented Sep 24, 2018 at 11:20
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.
