I have 2 SharePoint list,
1) One SharePoint list will save the data based on the user input from Nintex Form
2) Second SharePoint list (GSCData) is used as database.
When the user inputs client code from Nintex form it has to lookup from GSCData list and fetch the
memo no and sunrise/non sunrise to Repeating Section. In the below scenario i have updated Client Code and in the above GSCData list we have 2 line items which is related to "ARTH020" client. It has to automatically add 2 line items in Nintex Form Repeating Section.
Here are two post that talk about how to approach that. This can be done with JavaScipt which is possible in the product but not supported. Meaning you're on your own, but hey thats why you're in the community :)
I see you decided for responsive design...
if you'd like to show dynamic number of rows for a given client code you can forget to achieve anything like that in responsive forms.
if number of rows is constant, you'd need to add to the design as many controls as number of rows and columns you'd like to show.
if you're not stick to a repeating section, resp. you just want to show but not edit clients data you could use list view control - which would be much easier and straight forward solution.
but neither of those are available in responsive forms.
I appreciate your responding and offering advice, but not quite sure why the negative tone regarding responsive forms. It doesn't even merit this use case and Nintex provides options for different use cases as needed.
have a closer look at pictures attached to the question....
there are handles around the controls that are only present in responsive designer
I appreciate your responding and offering advice, but not quite sure why the negative tone regarding responsive forms.
that's not negative tone, that's simply fact.
my personal rough estimation would be it miss half the functionality of classic forms.
of course, there are as well advantages of responsive design, but IMHO limitiations outweight positives (so far)
sure, everybody can decide which of the two is more suitable for a specific use case. if one decides for or is obliged to use responsive forms s/he has to aware of limitations as well.
and so I provided hints for both possible designs