This is odd.  I have a drop-down list that is populated from a secondary
datasource.  In this case, a participant's ID is the value and their name is
what is displayed.  I want to store their name in another main datasource
element, so I created a rule that finds the matching element in the same
secondary datasource to which the drop-down is bound by filtering on the ID.  
However, when an item is selected the drop-down just resets to the first
(blank) item, and the other element is never set to anything.

Here is the XPath being used:

xdXDocument:GetDOM("Participants - Requesting
Managers")/dfs:myFields/dfs:dataFields/dfs:Participants_-_Requesting_Managers/@Name[../@BadgeID
=
xdXDocument:get-DOM()/my:AFE/my:GeneralInformation/my:RequestingManagerBadgeID]

I'm confused.  I've searched everywhere but all I have found was an example
of how to do exactly what I did
(http://blogs.msdn.com/infopath/archive/2004/09/10/227972.aspx), and
apparently it should work...Hopefully this is one of those times when I end
up slapping my forehead when I find the problem ;-)

Anyone have any ideas?

On a side note, I hope that InfoPath 2007 creates more efficient filters.  
i.e.

xdXDocument:GetDOM("Participants - Requesting
Managers")/dfs:myFields/dfs:dataFields/dfs:Participants_-_Requesting_Managers[@BadgeID
=
xdXDocument:get-DOM()/my:AFE/my:GeneralInformation/my:RequestingManagerBadgeID]/@Name

While this works the same way, it breaks the GUI, which will no longer see
the filter.  No biggie, but I have actually run into situations where this
can make a huge performance difference.