Altru Ideas

We value your unique insight into our products and services and often receive ideas and feedback from our community in a variety of ways. To streamline this process, we’ve created an idea bank where you can post product suggestions, vote for those most important to you, and add comments to existing ideas.

Suffix field for Membership WebForms

As an Altru user it is essential that we capture as much of a constituent's biographical data as possible at the time of transaction online.  Having the end user enter their generational or post-nominal suffix at the time of checkout will reduce back office data entry and cleanup - and it will create more accurate records.

WebForms should have a suffix field to account for this and pull its entries from the biographical suffix code table. End users with suffixes outside the predefined scope would be encouraged to append the suffix to the last name field.
  • Guest
  • Jan 4 2016
  • Reviewed
Constituent Records / Membership / Web Forms
  • Attach files
  • Laura Schmid commented
    September 12, 2019 15:35

    I absolutely concur on this matter. It would be helpful but also vital when you happen to have many generations of people dedicated to your organization! I just had to fix a membership transaction where the son (Jr.) bought the membership online but the transaction and membership went to the father's record (Sr.). They both live at the same address still so absolutely all their information first name, last name, address was the same. And because we had had some previous confusion between the two people previously, the son's email address was on the dad's record, which is why it linked to that record. But guess what--we can't delete the email address because it is linked to a sales order... another frustrating problem I'd like Altru to fix. If we can't delete the wrong email addresses from records, then this kind of problem occurs. 

    Attachments Open full size
  • +3

Related ideas