- AaronSchimannAsked on January 11, 2017 at 06:47 PM
This is happening when I attempt to duplicate multiple fields with conditions.
I have been working with Jotform for almost every day of the past 3 weeks and have not experienced this yet.
Can you please fix ASAP. I cannot work with the product operating in this way.
- CharlieAnswered on January 12, 2017 at 01:19 AM
Please do check your conditions, I cloned the form you have and it has more than 1,000 conditions. The problem is that you have repetitive conditions.
You only have 64 fields in your form, I am not sure how 1,000 conditions will work. Please review the conditions and delete those that are repetitive. Browser will have a hard time loading this much, there's also risk of having a lot of conditional conflict when your form is viewed live, causing the browser itself to crash.
Let us know if that resolves the issue.
- AaronSchimannAnswered on January 12, 2017 at 01:38 AM
Hi JotForm -
Sadly, this does not resolve the issue.
The form I sent is a much simpler form. You are looking at an invoicing form. This has never happened before, even with the more complex invoicing form.
Also, I have not previously seen guidance about a recommended maximum number of conditions.
I would appreciate you looking into this further.
- CharlieAnswered on January 12, 2017 at 03:18 AM
This is the form you shared in your initial post: 70080563539861. I cloned that form and that's actually the form shown in my screenshot.
If you are duplicating multiple fields with conditions, that's actually why the browser is crashing, you are trying to duplicate fields with multiple conditions. Even duplicating a field with 500 conditions on it would put too much load in a browser. We do not have a defined maximum limit on fields or even on conditions, technically you can add more fields or conditions, BUT the problem is the browser itself can only handle or process a maximum limit. Even our drop down fields have a maximum limit.
We had a case where a user has around 2,000 coupon codes in his/her payment wizard, he/she did not update or removed old coupon codes, that caused his/her browser to crash, even the live form.
There is no problem with the complexity of the conditions as long as it does not cause any conflicts or would stuck the form action to a loop, but in your case, the problem is more of the number of conditions and trying to multiply it more by duplicating.
If you open your conditions list, you'll already notice the unusual loading of the page. This is the same in my case, here's a screencast, you can see that my browser will be unresponsive when I try to duplicate a field:
The duplicate function does work correctly, here's a screencast of it:
Please also note that duplicating field with conditions will duplicate it as it is. Which actually means fields associated with multiple conditions will most likely be duplicated more. Example:
- Field 1
- Field 2
- Field 3
If you duplicate Field 1, Field 2, Field 3 you'll actually get 3 copies of Condition #1.
With that, the problem I believe is still related to the number of conditions and duplicates of it that you currently have, 1,000+ conditions is actually not ideal and is prone to errors, it will also be quite impossible to maintain the logic of it with that number.
I also checked your form "[CLONE] Varezy - New Invoice - 125 Union St" which I presume the form you are referring to that has a more complex condition? Note that that form only has less than 200 conditions, it does not put too much stress on the browser. Here's a screencast, I cloned that form and duplicated some fields:
You can see that I was able to successfully view the conditions list and was able to duplicate the fields with conditions.
However, note that this is not a good practice if you will not edit or delete conditions that have actually the same functionality. If you have 10 conditions with the same action on 1 field, it will be prone to error or conflict, and this action will pile up on more conditions that will eventually cause more issues on your form.
I hope this information helps. If this suggestion does not help you resolve the issue, I can forward this to our back-end to see what they can do.