InfoPath Dev

So I've got a functioning IP form with a repeating table that is sucessfully adding records and storing them in a SPF 2010 form library.  The form is a basic Project Request (PR) form, with the PR information and then a repeating table that allows different tasks to be assgned to different people.  The inserts are working like a charm and I can view/edit the data just fine.  The problem is that I need to be able to filter the form library based on the assignee.  So when a tech logs into the PR site, they can see what PRs they have tasks in and what the status of their tasks are without having to open every single PR.  The way the form library works, I can't get it to filter correctly and I can only see the info for the first assignee.

 When a repeating InfoPath field becomes a promoted property in a SharePoint form library, there are usually four options: first, merge, count and last. Sounds like you've selected first when promoting this property. You'll want to change that to last instead.

Still not doing what I want it to do. Here's an example of what I have:

Project #1  Make new user

Create user object - Assigned to Bob

Create user email acct - Assigned to Sue

------

Project #2 Delete user

Delete user acct - Assigned to Bob

Shoot user in parking lot  - Assigned to Vito

-----

Project #3 Promote user

Update user acct - Assigned to Sue

Shoot Bob - Assigned to Vito

------

If Bob logs in, he sees Project #1 and Project #2.

If Sue logs in, she sees Project #1 and Project #3.

If Vito logs in, he sees Project #2 and Project #3.

I'm confused by your last response, sorry. If this doesn't make sense below, my apologies.

Let's say you have permissions set up somewhere, or a filter based on assignee, and these are looking at the xpath:

/my:myFields/my:containerGroup/my:repeatingGroup/my:assignee

which is a repeating node and has three rows, Bob, Sue and Vito

then most likely permissions are granted to all of the three because those are the values in

/my:myFields/my:containerGroup/my:repeatingGroup[1]/my:assignee = Bob

/my:myFields/my:containerGroup/my:repeatingGroup[2]/my:assignee = Sue

/my:myFields/my:containerGroup/my:repeatingGroup[3]/my:assignee = Vito

You could create a separate field, outside of the repeater, and call it my:CurrentAssignee. This would be a single (non repeating) node that stores only the current assignee, and you could assign permissions or filter based on that xpath.

I've got a form with a parent/child relationship between the main form and the repeating table,  The main form holds the Project Request info, the repeating table holds the tasks and the users assigned to the tasks for the various tasks needed to complete the PR.  I need to have each user see the PRs that contain tasks assigned to them.  Going back to my example:

PR - Project #1  Make new user
 Task - Create user object - Assigned to Bob
 Task - Create user email acct - Assigned to Sue

------

PR - Project #2 Delete user
 Task - Delete user acct - Assigned to Bob
 Task - Shoot user in parking lot  - Assigned to Vito

-----

PR - Project #3 Promote user
 Task - Update user acct - Assigned to Sue
 Task - Shoot Bob - Assigned to Vito

------

If Bob logs in, he sees Project #1 and Project #2.
If Sue logs in, she sees Project #1 and Project #3.
If Vito logs in, he sees Project #2 and Project #3.

Each person sees only the PRs which have tasks assigned to them.