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 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
I can also attest to how beneficial this would be for our team.
With this idea being "Started", I'd like to re-emphasize that the ability to dynamically set the values of the repeating sections is what would be really key, for us.
Our largest use case would be in an equipment form. Users want the ability to either "Save as Draft" or "Edit" their previous submissions. Both requests are unable to be accomplished without the user having to re-enter that they've already selected, which is poor user experience.
With several users requesting this, and somewhat expecting this type of functionality, and us having to turn around and mentioning that it is a limitation of the product we are leveraging is not great for Nintex sentiment, especially with our leadership team who are the ones who determine if we continue using Nintex or not.
Any new updates on this?
The table feature seems useful only if you don’t have Sharepoint online or sql of your own. If you do have those things it honesty seems a bit pointless.
Having an editable repeating region would be directly useful in a lot more instances, at least for me.
As for plugins, no. Instead I’ve recreated the repeating section I need in Sharepoint, and used xml to populate to / read from that.
That’s part of why I’m surprised this is taking so long - the new responsive designer in Sharepoint already has this feature. It’s just a pain to have to mix and match - nwc for it’s database connections, so online for it’s ability to create a repeater.
Thank you for checking in, Drew! We are currently testing the table feature, but we do not have a set timeline for when the editable function will be available. Have you considered using a plugin to fulfil this capability? https://help.nintex.com/en-US/formplugins/Home.htm
Any updates on this? It seems like a relatively simple ask. All we need is a place to store the JSON generated by the repeating section, and a way to rehydrate the data into the section. We could actually do this back with classic forms in sharepoint on prem.
Hi Garrett, we had some internal feeback process which delayed us a bit into May for the release. Hope this feature is useful. I understand that we need them to be edittable but it is not currently in the near term roadmap due to other priorities. However you would be happy to know that we are currently working on Tables in NAC which will enable a lot of 'edit' scenarios for forms. I dont have specific timeline however we will be looking ro release MVP this calendar year.
12-May 2023 - The read-only Repeating Section feature has been released to NAC/NWC.
Still need to wait for the editable Repeating Section functionality to have any practicality in real world usage.
Any update on this feature? April 2023 is almost over.
I am excited to share that we will be releasing functionality for designer to reuse repeating section data from the start form into task forms within a workflow. Typical use cases involve task approvers who will be able to see the start form information in repeating section to make an informed decision (some described in comments above). Designers will be able to add labels and images to the reused repeating sections in task forms. At this stage we will not be able to support ability to edit the data in task forms. The feature is targeted to be released next month (April 2023). I will keep this ticket updated with the progress.
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.
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.
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.