Why on earth would Primary Alumni Class of not be a field? It is a major identifier as is maiden name. If someone updates for Jane Smith it could be 6 different people...but if Jane Smith indicates she graduated in 1977 or that her maiden name is Jones, that narrows it down significantly.

I am honestly not sure how those forms are attempting to identify existing constituents and how we are supposed to figure out for sure who is sending an update. We have a lot of new alumni who still live at home and their dad has the same name and grandpa with the same name has also moved in with the family and all are in our system. I use the class year a lot to differentiate between family members. It is essential with multi-generational families.

I can't vote for this enough and stress enough that we would love to move off of other softwares/websites that we use forms for, but there are not enough fields on the Constituent Forms to warrant us to use RE for this purpose. This causes our data entry process to be longer than necessary. While it's great this was released, the fact that we cannot use this for anything, but basic information and custom fields really limits our ability to switch over and use this fully.

Examples of what data needs to be included on constituent forms are primary employment, education, and demographics (All of the fields under these categories).

We want to use the form for an alumni reconnect form. We'd love to be able to add things like preferred name, name used while at the institution, title, maiden/former name, suffix, gender, date of birth (for identification purposes). Also things like campus they're affiliated with, major, employer, job title, preferred language, preferred method of contact, etc.

100% agree. When you add Class of, and Subject from Primary Education can be link to their education record not a custom field.

Instead of using custom fields to collect class notes/life updates can it link to the notes section?

Would love to see Preferred Name, Title, Middle Initial, Maiden/Former Name, Suffix, and Class Year. We'd like to use this form to collect class notes/life updates so having a space for this, other than Custom Fields, would be great.

Preferred name, Titles, some sort of ID matching would be useful (and prevent duplicates) - please store this in notes or custom field so data is not lost if not able to be matched directly.
Also include option for mobile and web links (to collect social media).

We primarily use Preferred Name when we communicate by email to our stakeholders so would be more than nice to have this field, plus title, birth date, employment info in the forms.

Yes! More fields are needed. Please add Maiden/Former Name, Preferred/Nickname and Class Year. These are important for us to be able to match and update the correct record. Employment fields of Organization Name and Position would be great to have on these forms as well!

Would be nice to add more specific fields - date of birth, maiden name, class of, degree, title. Also, would like to see a spot for employment information and life updates such as marriage, birth, death.

Suffix and class of are MUST haves as well as it must be sent to review for updating, not processed/matched automatically please!!

It would also be nice to have a free text bubble option, like reference in a gift form, that can be used for collecting a specific data point. Maybe this could come across as a note in the "transaction" on the constituent form confirmation email.

Currently you can add constituent custom fields to the form, but it would nice to be able to add any custom field to the form. I currently have a "Class of" custom field but for donation forms. I couldn't add it to the constituent form because its for "gifts". It would be great if they could be used in either place instead of having to make a duplicate custom field/table.

Definitely this! Class Of and Subject at minimum - even if free form rather than matched to existing fields in RE. Custom fields isn't an area we utilise in this way.

@Samantha we would want to review them as per the comment from James. We wouldn't want them to be automatically updated. This is purely for us to use as a way of matching the person with the correct record. We just need them to be available as fields we can add to the form. Ideally the title and suffix fields should also be available on all forms where a name is required, ie when an invitee is able to add a guest to a registration form at the moment there is no way to include the title and suffix for their guest.

@Samantha, from my perspective, if there's the ability to review this before adding/updating a record that's preferable. We have specific processes for adding/updating education records, and having it done automatically will create some additional maitenance for us...though other users might do it differently.

Thanks for these suggestions! One question - for the fields of "class of" and "primary education subject" you note you want these for identification purposes. Would you want these fields written into a new or updated constituent record?

How about just more fields! All the 1:1 fields? Let us pick, like in Lists when we select filter/column fields. I thought it would be great to be able to use a Constituent form to help us connect with families encouraging donations in lieu of flowers in memory, so we can provide tribute acknowledgements, and better prepare for the tribute, but with so many limitations on the form, it doesn't allow for anything more than an address update.

We need suffix! Quite frankly, every online form through BB should have the suffix field added as an option for the donor to enter and to use in matching.

Yes, other fields are needed to determine which record it actually is. Even for a small school we have so many constituents with duplicated names, and the Sr./Jr/III issue.

The suffix should also be added as an option on the form