I'm not sure I get what you want to do.  Maybe you could explain the concept again at a little higher level? You talk about forms but this is XPages right?  You want to maintain everything via XPages?  How are you limited by your current approach?

Let me change the concept slightly to try and explain back to you...  I'm not sure if I'm right or not...

Say this is a Project and task tracker.

You want a main document for the Project and then sub documents for each task.  the Task document  has a "Type".  Whatever, but lets say "Clean", "Purchase", "Delivery".  You want to create a task against a project and choose from Clean, Purchase or Deliver.  Each task will also have a comments field and a checkbox.

BUT you don't want to be limited to "Clean", Purchase and Deilvery".  A project could have ANYTHING for the "task type".  You want to maintain the list at the project level..  then when you make sub documents you want the type to pull from this list on the project document?

Is that close at all?  or not really?

Dave

Sorry for not being clear, and thanks for the reply.

I have to change up my vocabulary with forms/documents

If I take your example of a project/task list.

The tasks are maintained by a superuser who creates a new document for each item. Each document contains 3 fields and lists the place and category for the document (example: 1, hardware, itemName).

The project contains a collection of all of the tasks (uses a dblookup from a view that roders the items, and displays them in a checkbox group) that have to be completed for each task. The tasks are not able to be changed by the end user (only the superuser can maintain the list.

Currently the user checks each item, then it saves the value of the itemName into the multi value field

What I would like is for each task item to have the ability to add some additional information. I would like to have another field for comments that would be tied to each task item, and another checkbox. All of this data needs to be saved to the project document, as the task list operates almost like a profile document.

My thinking here is that dynamic fields in a repeat would be the answer. I use a repeat control to collect the data and display each itemName. I would then use dynamic field binding to have the field name for the comments be "itemName+comments". so when saving the document I add a comments field for each item.

I have done inview editing before(in xpages), but my previous experience has me accomplishing this with multiple documents, with one document for every row. This might present a problem in this case as I would be creating 50+ documents for each project.

Does this make sense?

Pat,

Not sure I totally get it so I'll make some random comments that may or may not be helpful.  I'm really not sure what you mean by "dynamic fields". I'll assume this is an xpages only app as well.

I'm hearing a Project...  and Tasks...  So I'm thinking a project document and multiple task documents related to the project.  Now when I relate documents in xpages it's NEVER with response documents.  It's always with a shared key similar to a relational db really.  On each task item I'd have your comments field and checkbox.

So from the project you can create new Tasks (documents) from whatever list of valid tasks that you maintain.

You mention " All of this data needs to be saved to the project document" .  I don't get that.  Is there a need that all the data be saved onto a single doc?  Remember in xpages you can have multiple documents on the screen at once.  So it can look like it's all the same "document" even though it's not.  I'd have a project with a repeat control of the tasks...  button for new task etc...  ASSUMING I'm not missing anything.

If you really do want to save everything back to a single project document...  I'd recommend looking into mimeBean..  from Jesse Gallagher...  but that's a more advanced concept and might not work in your application well if you need to do a lot of searching and stuff.

Just some thoughts...

Dave