I vote for this but duplicate mailings is never an issue if you use RE properly. What IS an issue is soft crediting, reporting, and analysis.

We just add them as a Guest of the spouse who is an Constituent. I agree with Melissa about the main issue with adding spouses as Constits is soft crediting, reporting & analysis. So, I always try to avoid adding Spouses as Constits.

We don't need to add them as a constituent, just a guest, however - it would be totally awesome if you could pick the spouse as their guest so we can bypass having to retype their name - we've had instances where the name was mistyped - having this functionality would ensure the correct spelling is used and needless to say - it would make sense! Thanks!

Being able to add a non-constituent spouse as AT LEAST a guest for a participant is very much needed. All Participants get an entry in the Records table anyway, why not be able to link those non-constituent records (rather than creating yet another duplicate non-constituent record) the same way we can in Relationships?

I think this goes for any non-constituent relationship. Event guest data entry is very awkward.

This issue is driving us to not use the Event module at all! We would get so much use out of it if we were able to add people who are spouses or children but not constituents.

It certainly would never drive me to not use the Event module. It may cause me to either a) create non-constituent participants that are unfortunately not linked to the non constituent relationships or b) change my policy on allowing spouses to have full constituent records if they attend events. The event module is too awesome not to use.

Events should do like the tribute module does - allow you to pick from anyone in the relationship tab and make them a guest (like tribute does for acknowledgee).

I just ran into another issue with the inability to add non-constituent Participants. It becomes impossible to Query or Segment across multiple Events and avoid duplicate output if the Individual or Organization has multiple non-constit Participant records. Admittedly, if they have participated in multiple events it is probably time to give them a full Constituent record, but I'm also not finding any way of determining who might fall into that category because I, again, can't find/link that existing non-constit on future Events. I'd have to manually compare lists of all existing Participants to try to find the dupes.

I am being forced to deviate from the core concept of our database design (spouses as one constituent) to account for this and it is creating problems in a number of other areas like mailings, gift reports, constituency giving reports etc. I am leary of revising my whole database structure, but the increasing lack of consitency is becoming more and more problematic. Not to mention the additional time it takes to create a new record and add all the tracking mechanisms to keep the records linked and account for some of the mailing and gift reporting issues.

If we chan choose nonconstituent's from the relationship tab in the Tribute Module, then why not the Events Module? Consistency is the #1 factor of accuracy, and should be the #1 factor of design as well.

As you can add a spouse to a constituient record can you make it so you can pick up 'spouse' when registering a guest for an event at the point where you pick individual or organisation. This would be really helpful.

This is so true and we are also considering spliting records (which we dont want to do) becuase of this problem.

This is basically the same topic. Maybe we can consolidate

http://rediscovery.uservoice.com/forums/137015-raiser-s-edge-discovery-topics/suggestions/4577558-event-module-link-non-constituents

You can link constituents to non-constituent relationships in RE, which is a very good thing. If the non-constituent becomes a constituent at some point, BOOM! All of those relationships are there. This should apply to event participation as well

Does BB even look at our requests? This issue has a high number of votes, but it has not been addressed sine 2012.

A high number of votes, yes, but it's still #25 overall. Sadly the optional modules, by their very nature, will probably get very little attention. And with the huge problems from the 7.94 roll-out (despite it being released almost 6 months after it was supposed to be released) combined with the release of NXT, I doubt we'll see many (if any) of the remaining suggestions implemented. There are only 4 topics currently "in discovery" and the most recent of those is from Feb. 2014.