I have a case where i need to create two lists probably..... The first one will contains a general submission data while second list will keep the sub tasks with additional info. Generally speaking the first list will contain one row while second many rows related to one and only row in the firs one. This is like in one-to-many in relational database.
The picture is representing the case that I would like to achieve using customer and customer rentals as an example.
Now i would like to have a possibility :
- store and present data in on form
- update the list or list while editing
- manage access of inputs on the form from list #2 fields depending on choices and person fields.
Presently I'm using one list with the multiline column in list#1 for data that I treat as list#2.
I used a repeating section on the form connected to multiline column in the list#1 and the values are stored there in xml format. But with this solution when I create a rules on the form, the form stops working - more over stops to display showing blank page.
Any Idea how to solve it? shoul I focused on two lists or stay with one,..
This is a large and sort of complex problem to tackle. The Nintex project I'm in charge of is a one to many style setup, and there are significant hurdles in getting it to work with Nintex depending on exactly what you'd like to do.
The main things that I feel really qualify whether or not it's a good idea are
I feel like if either or both of those questions are "yes" then it's a good idea to consider digging into the creation of a Many to One style setup.
While this is by no means a complete answer, I highly recommend looking at Vadim's example of building a Many to One style setup using an Order and Order Items relationship: http://workflowexcellence.com/nintex-workflow-order-and-order-items-relationship/
If you do decide to go down this route, here are some of the things that I found myself having to consider and solve. Some or none of these may apply to your situation, but I figured they were at least worth mentioning
That's about all I can think of for now on the subject. I know that I have written a lot about it here and it may look daunting, but I just want to pull things into perspective depending on how deep you'd like to venture down the rabbit hole. If your case is solved by the video / blog I linked above, then that's awesome, but if you wanna go further with it, then the questions I've written above will likely need to be answered as they are all things that I've had to answer for my own project.
I hope this helps you with some of what it is you're looking for / to do