InfoPath Dev

I've created a master/detail control in the main view for my form.  I need to create a dedicated view for this master/detail control; however, when I create a new view I encounter the following issue:

1) After configuring the master/detail control in the main view (in this instance, a collection of text box controls inside group 72 and nested within group 71), I create the new View.

2) In the new View, I attempt to drag group 71/72 from the Data Source panel of the Task Pane to populate the new View with my master/detail control.  I select Repeating Section with Controls so all the controls will autopopulate.

3) The result is a Repeating Section (detail) but no Repeating Table (master).  The control is masterless.

What steps do I need to take to outfit my dedicated View with the entire master/detail control?

Thanks,

JMR 

You need to create a repeating table and a repeating section both bound to your repeating group.

On the Master/Detail tab of the table's properties, indicate it as a Master and give it any Master ID you like.

Then on the Master/Detail tab of the repeating section's properties, indicate it as a Detail, and select that Master ID from the dropdown.

That's it!

I appreciate your prompt response.

To be clear: I should create a new group (rather than re-use group 72) in my new View consisting of a repeating table (master) and repeating section (detail) and then set the master/detail relationship using the Properties dialog - correct?

My thought was that all controls and groups needed to be created in the main view so they would be part of the myFields XML schema.  In the past I created controls in separate views and then wasn't able to print them.  Can you clarify?

Thanks again.

No, I think you should reuse group72.  Drag it with the right mouse button into your new view and choose Repeating Table, then drag it into the view again and select Repeating Section.

Fields do not have to be represented or created the main view to be included in the myFields schema.  They don't have to be present in any view at all.  You should be able to print anything that's present in your print view.

And I would suggest using more descriptive names for your groups and fields in the future. A good practice is to design the data source first, and then create controls from it, instead of having the fields automatically created with default names.

That worked.  I've done that successfully in the past but not with a Master/Detail control.   

Thanks very much.