Yes, in the example XML fragment below, I would get multiple print outs of [First item, GroupA] even when I filter under GroupB
..and then this problem will go away, ie. rebuilding the xsn from exactly the same xml will remove the problem. This is why I thought of mentioning the problem, to see if any poor souls had had experienced a sort of 'hicupping' behaviour in the underlying xml parsing of the data source. Of course, I understand the possibility of a circular reference in the xml etc. but I would expect consistent behaviour in the rendering
Confusing..
<Node4 StatusFilter="Open">
<Node5 Type="GroupA">
<Item Id="1">
<Question>First item, GroupA</Question>
<Answer></Answer>
</Item>
Item Id="2">
<Question>Second item, GroupA</Question>
<Answer></Answer>
</Item>
</Section>
<Node5 Type="GroupB">
<Item Id="1">
<Question>First item, GroupB</Question>
<Answer></Answer>
</Item>
Item Id="2">
<Question>Second item, GroupB</Question>
<Answer></Answer>
</Item>
</Section>
<Node4>