InfoPath Dev

I've got 4 columns in a repeating row that populate from a ishare list. I want to add a fifth, but a blank one that the user can type into. So, the first 4 columns of this repeating table will be auto populated, for everyone one of these rows, however many there are, I want the fifth column to be a blank text box that the user can type into. That is, the other columns have no effect on it nor does any other option or rule. Simply an empty text box the user can type whatever into.

My issue, if I bring a Main field into a repeating field, it seems to work at first. But, since this field only gets stored in one place, if it gets changed in one row, all the rows change. Obviously this is not what I want. I want each of these blank fields in it's respective row to be independent.

My other idea was to add a blank field to the ishare list, then bring it in just like the others. However, then the user cant change it and it remains permanently blank, which defeats the purpose. unless someone knows a way around this?

a visual for what I want: Columns ABCD are autopopulated from an ishare list and work fine. E is the independent repeating blank but changeable field for the user.

A1 B1 C1 D1 E(somthing typed)

A2 B2 C2 D2 E(something else typed)

A3 B3 C3 D3 E(A third and different thing typed)

here is what I've been getting:

A1 B1 C1 D1 E(somthing typed)

A2 B2 C2 D2 E(same as above row)

A3 B3 C3 D3 E(same as above row)

This is one of those challenges with InfoPath. If your data is a secondary data source, then letting the user change it won't persist (you can't out of the box submit back to it). But there is no rule based way to insert rows. Effectively what you need is to copy your repeating data into the main data source and have an additional field that the user can type in - or simply display the secondary data in a main data source repeating section. I'm attaching an example that uses default values for this - save it locally, right click to select design, then preview.

I'm in a pretty strict office, we are blocked from downloading files like that, anything with a banned file type, which is like everything. Could you explain the process in more detail? your first suggestion sounds like creating a main field for every value that can be inputed with validation/hide rules. Can't do that, too many possibilities, not sure if thats what you meant though. Also, what I did with the secondary was drag it straight in from the secondary source, how is this different from "or simply display the secondary data in a main data source repeating section"?

In my sample, I set the default data for my repeating main data source to include 4 instances of the main repeating group (this technique relies on having an idea of the max rows that will be returned from your secondary data). Then I used calculated values with a count of preceding-sibling main DS rows to display the secondary data next to the main data source field.

The way this is different from dragging your secondary data source onto the form is because the main data source is the only place we can save data. Having the repeating section bound to the main data source means the user's entered data will be saved in the XML from the form.

That helped, feature is working.

Much appreciated