InfoPath Dev

I am setting up a situation that looks like this:

The three fields are in a repeating table, and the Deliverable field is in a repeating table embedded within the main table.  The idea is that you have one milestone, with one date and multiple deliverables assigned to that milestone.

This setup works fine for the main data entry view, however, I have another view that I want to look like this:     Deliverables    |   Parameters - where Deliverables is populated in the prior view and Parameters is unpopulated

and another one that should lool like this:     Deliverables    |   Parameters   |  Results  - where Deliverables is populated in the main view, Parameters are populated from the second view and Results are unpopulated

In the second view, I want the  Deliverables field to be read only and listed out as entered from the main view.  The Parameters field, however, should allow the user to enter in text - unique to each separate deliverable.  So in other words, as I add deliverables in the main view, empty, editable fields appear to the right of deliverables in the second view, ready to fill with text.

 In the third view, I want essentially the same thing, only both Deliverables and Parameters are read-only and the Results field has replicated to match Deliverables and Parameters.

Here is a screen shot of my field structure:

 I know this should be able to be done, but I've been hacking at for three days now and I'm at the end of my rope.

Please help!

Thanks,

Thomas

Show us your template maybe?

How do I attatch my .xsn to this thread?

You can attach files to posts in the Options tab (don't use Quick Reply).

Have attached my .xsn - had to pare a lot out of it though, but the meat and potatos of the issue are still there.

This is involved enough that I'll have to work on it after work, but maybe one of the Qdabra folks will be able to review it during the day.

warrtalon:

This is involved enough that I'll have to work on it after work, but maybe one of the Qdabra folks will be able to review it during the day.

I really appreciate the help.

warrtalon:

This is involved enough that I'll have to work on it after work, but maybe one of the Qdabra folks will be able to review it during the day.

I really appreciate the help.

 Try this link - I uploaded the whole file (400k) to the OfficeLive.  Or, if this doesn't work, I can e-mail you the file at your liersure,

http://workspace.office.live.com/#pACQxODEwYWJlMS1lNzEzLTQ2MDktYmU0ZC02MjAzOTIzNzJlZWYAe--vk73jfsVJrVjgOVERwiZ9ABx0aG9tYXMud2FsdGVyQHdoaWRiZXl0ZWwuY29tABRcLZg-2qOrSyiQyaUGL87M3RxcDwAA 

So forgetting the jargon for a minute, this is the data flow I want to achieve in InfoPath: 

There is a One to Many relationship between Milestone and Deliverable

There is a One to Many relationship between Deliverable and Parameter

There is a One to One relationship between Parameter and Result

No matter how I try to put this together in InfoPath, I can't seem to get it to work.  This is not tied to any database either, it's a self-contained form published on a sharepoint site.

Thoughts?

I think I got it.  It does what you want as far as I can tell, but it's not pretty in that the Deliverables/parameters/results are not all on the same line going across, however, they are clearly sectioned off and associated with their respective parents.  This does the relationships you wanted, the views you wanted, and the read-only nuances.  I had to make a new XSN from scratch, because yours could not be modified easily to do what I wanted...

If this works for you, I'll accept payment in the form of a visit to my Blog.  =P

GENIUS!  Sheer genius.

 Took your example and integrated it into my form.  Works like a charm.

Thank you so much for your help - you rock.

Thomas

Great.  This was also good for me, because I did not know the answer for sure at first but had some ideas, and they worked on the first try.  This is knowledge I will be using well into the future.  The funny thing is that I had just gotten that nugget of knowledge earlier in the same day from one of the Qdabra sample forms.  Still learning every day...

Pray tell, what form was that? We need to Twitter your blog on how to do this. Care to write the blog first? :)

I was referring to the qRules demo form from the video, but I later realized I had actually learned the concept while playing with the GetCommonMemberships method of the UserProfileService, which by the way is VERY useful and will be replacing my older method of mimicking the User Roles functionality in browser forms.  I am going to start changing that blog post tonight.

Do you think it's worth writing a new blog entry on this concept of nested repeating and non-repeating groups and fields for the purpose of creating both one-to-many and one-to-one relationships all in the same table?  I had thought I was just late in coming to the understanding of how that stuff works, but perhaps it's not so common knowledge.

It's all good. This isn't the most common issue, but we see a lot of issues related to badly formed data sources.