Under my account you will see a form called "2011 Register." The form itself works great, as does the information loaded into the back end when I view the responses. My issue comes with the Email Notifications for the form, both the admin notification email and user notification email have a display error. This applies specifically to my Team Roster --> section --> section, which is a repeatable grid row. Currently I have HTML enabled which I am changing to Text to see if that makes a difference. The display issue is this:
A user adds 16 additional rows to the repeatable grid row section, and enters the 17 names of each of the team members on their roster. Whichever name is added in the first row (not the first added grid row but the actual default first row of the entire grid section) is then added to the end of the section list (within the email notification) 16 more times so that there ends up being a total of 35 rows listed in the email notification. I can forward the email notification to you if desired so you can actually see what I see in case my description is too confusing. Any ideas on how I can prevent this from happening on the email notifications? Thanks!
Again, I will be testing taking it off HTML and making the email notifications Text only.
I can confirm that this issue does not affect the Text Only version of the notification. Although the format for the Text Only version is horrendous so please fix this issue between the repeatable grid row section & HTML notifications. Thanks!
Great thanks. Hopefully its an easy fix because most of those that submit information on my form end up emailing me about their notification. That notification is there actual receipt of registration so they are rightfully concerned as to what happened. But at least it is only a display error and not charging them for extra registrants. Thanks again for the response.
We've recently pushed an update to some of the notification code. Can you: 1. Make a copy of your form. 2. Switch over to the HTML notification on the copy. 3. Run a test.
and let us know if the problem is resolved? If it is not, open a support request and let us know the form id for your copy form, and I'll take a deeper look.
OK my support test form ran directly from formassembly seems to be show this issue has been resolved. Of course my original form still has the issue because I have not re-copied the publish code to my own site (where folks are utilizing the form). I will copy the code back over and run some more tests. Thank you!