Date of Birth field not enforcing requirement during Registration

Options

Hello,

 

We have the DOB field included & required for all of our TR blueprints and for each participant type. However, returning users seem to be bypassing that field and no error message is stopping them from proceeding to the next step.

 

Any ideas?

Tagged:

Comments

  • Kent Gilliam
    Kent Gilliam Blackbaud Employee
    Ancient Membership 2500 Comments 100 Likes Name Dropper

    Melissa,

     

    I think this is simply an issue where the returning user already has a record so the system doesn't take them through your registration flow where this question is now required. The only thing I can think to do would be to add some sort of conditional content in your autoresponder to the returning user. Basically it would test to see if the birth date was present and if not it would render some content. It would look something like this:


    [[?xx::x[[S1:birth_date]]x:: <!-- Message for person that doesn't have birth date info --> :: <!-- Message here for person who does have birth date info (can leave blank) --> ]]

     

    You can include a message with a link to a survey form where you can ask them to enter their birth date. Make sure you have the auto-login configuration done. I would recommend including an email field and a birth date field so if the auto-login doesn't work then the system can still match the birth date to the record using that specific email.

     

    Hope this helps. Unfortunately it's the only way I know to work around this.

     

    Kent

     

     

     

Categories