Conflict when using required fields and page breaks

  • Profile Image
    Asked on December 25, 2015 at 07:17 PM
    2) Apparently, there is some sort of conflict with using conditional statements along with read-only fields. For example, fields 114, 117 will reset when going to the next page if id109 is read-only. The same goes for input249 and input 251. If marked as read-only, they will reset when going to the next page, messing up my subtotal. I unchecked read-only for now so it works, but those fields really should be read-only as they affect pricing. Technically this is for an estimate and deposit so maybe I could live with it temporarily, but something is not right with the logic. there’s no reason why a read-only setting should break the form. please check into this and get this fixed.
  • Profile Image
    Answered on December 26, 2015 at 02:24 AM

    Could you please share us the form and the steps on how to replicate the problem? I understand that you have shared the field # and the IDs, however, it is quite hard to easily identify them.

    You have also mentioned two forms in the original thread, here they are: 


    It would be best to state what form and the field label names, for us to replicate the problem.

    We'll wait for your response.