Expandable tables with user entered values that change to a Protected state after adding an instance of a subset of pages | Community
Skip to main content
nowackem
nowackem
New Participant
May 12, 2021
Question

Expandable tables with user entered values that change to a Protected state after adding an instance of a subset of pages

  • May 12, 2021
  • 13 replies
  • 2360 views

Using a subset of two pages, I have programmed a 2-page dynamic form to "Add an Instance" of said two pages by clicking a button. Basically the 2+(dynamic) pages can repeat in proper order infinitely. On page 1, I have a table with repeating rows which works fine. The issue is that I need this table to show the user input values in the repeating rows when another subset is added BUT (here is the kicker) make it cumulative. So if the user added 2 instances of the row and put values in these 2 repeating rows on the #1 subset of pages, I need these to change their state to protected and keep the values on the #2 subset but have the table still be expandable below those values. If the user adds 2 more values on #2 subset then all 4 rows with user input values show up protected on the #3 subset of pages and so on. Because of the cumulative nature of this particular form, all user added values need to stay in proper order. This was hard to explain so please let me know if I need to try again. My file is at the link below. 

https://drive.google.com/drive/folders/1Hom9xW6S4QT7Pee6RuTb1NW6zGb5RNJv?usp=sharing

 

Does anyone know if this is possible or maybe willing to check it out? This might be beyond the limitations of Designer but I wanted to run it through you guys first.  

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    13 replies

    Kosta_Prokopiu1
    Kosta_Prokopiu1
    Employee
    June 15, 2021

    Hi @nowackem, sorry that I did not respond to this earlier. Real life and work did take all the time I would have for things like this form.

    I did attempt to implement your logic. At first it looked as if I was succesful but then I realized that on the following sections I did get the wrong sums, the dependencies between the various sections and sums proofed a bit more complex than I had thought initially.

    So far I have no solution for you that fits into this form. And at the moment I do not have so much time to invest in this. When things quiet down I can have a look again, but that might too late for you.

    Regards

    Kosta

    nowackem
    nowackemAuthor
    New Participant
    May 28, 2021
    @kosta_prokopiu1 I just wanted to check in and see if you had any progress with this form? Thank you again for your assistance!
    nowackem
    nowackemAuthor
    New Participant
    May 14, 2021
    Yes that is correct.
    Kosta_Prokopiu1
    Kosta_Prokopiu1
    Employee
    May 14, 2021
    Let me express what I think you want: Your accumulated totals should grow with every Affidavit instance. If you have 3 instances, page total of first is 20, second 30, third 40, you would like the 1st Affidavit to show accumulated 20, the second 50 and the third 90. When changes are made in the first affidavit (lets say we add 10$) then the totals should show 30, 60, 100 - is that the correct behaviour?
    nowackem
    nowackemAuthor
    New Participant
    May 14, 2021
    Oh and I didnt answer the other part of the question. Yes TotCostAccTot needs to accumulate through all Affidavits.
    nowackem
    nowackemAuthor
    New Participant
    May 14, 2021
    in the Hierarchy its subsetAffidavit > Page1 > Page2. I had to make a Page1 and Page2 so the subsetAffidavit would repeat correctly.
    nowackem
    nowackemAuthor
    New Participant
    May 14, 2021
    sorry. in my comment Page is Affidavit. UGH this terminology! I'll try not to do that again. 🙂
    Kosta_Prokopiu1
    Kosta_Prokopiu1
    Employee
    May 14, 2021
    Just to understand this correctly: Page is/is not Affidavit? Do you mean pages that are generated by adding rows to your tables inside ONE Affidavit instance? The CostAcctTot field is to add over all Affidavits?
    nowackem
    nowackemAuthor
    New Participant
    May 14, 2021
    I think so. I just need those user added rows to accumulate throughout the entire form no matter how many pages they add. I'm realizing that my bottom totals are not working now either. I only need one totals row if we can make this work correctly. I think when troubleshooting I messed those up.
    Kosta_Prokopiu1
    Kosta_Prokopiu1
    Employee
    May 14, 2021
    instead of protecting the fields, if I show you a way to calculate all numbers only on the respective Affidavit instance - would that solve your problem and still allow changes?
    Show more replies
    Terms & ConditionsAccessibility statement

    Loading footer...