Skip to Main Content
Nintex Ideas

šŸ‘‹ Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!


If you are looking for the Nintex roadmap, you can find that on Nintex Community

If you have questions about Nintex Ideas, please contact ideas@nintex.com

If you require support, please visit Nintex Customer Central

If you have a sales inquiry, please contact sales@nintex.com

Status Planned
Categories Form Designer
Created by Guest
Created on Apr 7, 2022

Repeating Section or Tables for for loading dynamic data

Nintrex Workflow Cloud needs a method of re-populating repeating sections or use of dynamic tables. My scenario is as follows: a form is completed and may have a repeating section field with one or more rows; the data is stored, including data about bow many rows were created in the repeating section. Later the data is retrieved and needs to repopulate the fields so the form may be amended in some way. I am unable to do this with the current form tools. Tables are a defacto part of many forms and I don't understand why they aren't available in Nintex WC; similarly I find it strange that I am able to store the number of rows in a repeating field, but not pass a dynamic or conditional value for the default number or use some other control to set the value dynamically.
  • ADMIN RESPONSE
    Sep 7, 2022
    Thanks for the idea. Ā Opening this up for voting by other users.
  • Attach files
  • Deon Smit
    Reply
    |
    Nov 24, 2022

    This is really a massive shortcoming in the product imho. There is no way to show/allow updating of data entered in a repeating table for task users in the workflow. The same for Multi-value choice controls, attachment controls or any control other than single text controls. We have to spend countless hours implementing work-arounds if we want task users to be able to update submitted collection data.

  • David
    Reply
    |
    Sep 7, 2022
    I'm an NWC user and I endorse this message. I have a use case right now for which I'm going to have to develop some kind of workaround: it's an equipment order with repeating sections to capture item number, description, quantity, etc. When the order is sent to be processed, I need a way for the processor to be able not only to see each item ordered but also to make a notation for each item (such as "backordered," "fulfilled," etc.). In the task form for the processor, I can render the repeating section data in a table, but giving them a way to add to this data (with the aforementioned notation) is definitely a challenge with which I'm still grappling.
  • Anne Collier
    Reply
    |
    Sep 7, 2022
    We can't use NWC for most of our workflows due to the lack of this functionality. A state machine is virtually useless if each branch can't see and update the data entered in repeating sections by users in other branches.

    I was shown how to grab the xml and put it in a label to display it as a table, but that isn't editable. I was subsequently shown how to use a component workflow back to O365 to populate a form there that is editable, but what's the point of that if I can just create it in O365 in the first place?

    I really like NWC, it does have some really nice functionality and the speed compared to O365 is wonderful, but we won't be able to use it for anything but the simplest of workflows until this is implemented.
  • Jordan Maynor
    Reply
    |
    Sep 7, 2022
    This is a big thing holding us back from implementing a lot of our manual processes in NWC without having to do less-than-ideal work-arounds or simply disallowing the editing of data once it's past the initiator.
  • Guest
    Reply
    |
    Sep 7, 2022
    I've got a few rather large forms that need to go through a chain of command. Repeating sections would be ideal, but I can't use them because there's no way of pre-populating the fields (you can use default value, but each row would have the same value).

    If we could pass a form on with all that workflow's previously answered values onto another step, that would really help. Currently I'm using loops for the levels of authentication, so simply being able to pre-populate with values and indexes would help.

    As a result of not being able to do this, I've got a really labour intensive workaround, using static fields.
  • Guest
    Reply
    |
    Sep 7, 2022
    Quite useful.
  • Guest
    Reply
    |
    Sep 7, 2022
    We have a use case where we need to gather specific files from our Merchants for each repeating section. E.g. Each store could have a different menu. NWC does not allow ā€˜File Uploadā€™ control under the repeating section. Today, we have no way of collecting different files based on different information added in each section.