- VolleyballQLDAsked on January 18, 2018 at 01:23 AM
I have a form for membership where the cost is determined by age and level.
The "Age Category" is a text field, worked out by conditions on the "Date of Birth" field - seems to work fine.
I have the fees set up as calculation values in two multiple choice fields, one for adults "AdultFees" one for juniors "JuniorFees". Normally these fields would be hidden but I have them showing at the moment for testing.
The level is chosen from a radio button field "Membership Level". These three fields all have the same options.
I use conditions to insert the membership level into either the adult fees or junior fees and then insert the value into "Membership Fee".
I had set this up in my main form after testing showed it worked, and published more than a week ago and have had over 20 submissions without a problem.
Then yesterday my colleague's form had a problem with calculation and I tried out my form and found it too had a problem. Because my main form has many fields I pulled out the basics into a test form, which is the one I have included here.
The problem is that basically you need to click the membership level twice to get the right fee. It's like the insertion into "Membership Fee" is one click behind. You click Full and get nothing, you then click Rec and get $75/$35 (the Full fee). You then click another option (or same option) and get the Rec value $40/$20. ETC.
I have tested on various browsers, and on computer and mobile and get the problem on all of them.
Am I doing something wrong and for some strange reason the form worked the way I wanted the first week it was up?
Or is there a bug?
Please let me know how I should get this to work.
Hoping I have given you enough information.
Jill KellyPage URL:
- JotForm SupportNik_CAnswered on January 18, 2018 at 05:02 AM
I tested your form and I was able to replicate this issue.
So I will forward it to our backend team for additional checking.
We'll inform you further through this thread.
- JotForm DeveloperjanberkAnswered on January 23, 2018 at 07:50 AM
Hi, this should be fixed now. If you have further issues please let us know.