I'm sure others have hit this, but I've never had to really fix it before
and I am not as good at XPath or XSLT as I should be, so this is probably
trivial. Searching for solutions is not turning up much for me so far. A
simple trace causing me pain and suffering (and weeping, and wailing) follows:

Code:
--------------------
<nds dtdversion="4.0" ndsversion="8.x">
<source>
<product edition="Advanced" version="4.0.1.0">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
<input>
<modify class-name="User" from-merge="true"
qualified-src-dn="O=tstidm\OU=Users\OU=Empl\CN=sann"
src-dn="\TEST_IDM\tstidm\Users\Empl\sann" src-entry-id="98089">
<association>30992</association>
<modify-attr attr-name="workforceID">
<remove-all-values/>
</modify-attr>
<modify-attr attr-name="middleName">
<remove-all-values/>
</modify-attr>
<modify-attr attr-name="lenelinternalid">
<remove-all-values/>
</modify-attr>
<modify-attr attr-name="Surname">
<remove-all-values/>
</modify-attr>
<modify-attr attr-name="imgdatatype">
<remove-all-values/>
</modify-attr>
<modify-attr attr-name="lenelobjecttype">
<remove-all-values/>
</modify-attr>
<modify-attr attr-name="imgobjtype">
<remove-all-values/>
</modify-attr>
<modify-attr attr-name="Given Name">
<remove-all-values/>
</modify-attr>
<modify-attr attr-name="Surname">
<add-value>
<value timestamp="1377877424#1564" type="string">Ann</value>
</add-value>
</modify-attr>
<modify-attr attr-name="Given Name">
<add-value>
<value timestamp="1377877424#1562" type="string">Sunny</value>
</add-value>
</modify-attr>
<operation-data/>
</modify>
</input>
</nds>
--------------------

The problem is that the XSLT in the output transformation policyset is
matching on the first instance of the attribute which has no value, so the
CSV has no value in that field when I want it to skip over the
remove-all-values bit and instead get the attribute that actually has a
value. A possible solution is to strip out the remove-all-values portion
so that the only possible match is the one with a real value. Any good
ideas on how to implement this? It can be XSLT, or XPath, or something in
policy that I haven't remembered... whatever.

Thx.