A Forum reader recently asked:

“Is there any way, without resorting to XSLT, to strip all null values from all operations, either at the Input, Output, the Command or both?”

And here’s the response from Will Schneider …


I use these rules:

<description>Strimp Empty Values [Add]</description>
    <if-operation mode="case" op="equal">add</if-operation>
    <do-strip-xpath expression="add-attr[value='']"/>
    <do-strip-xpath expression="add-attr[not(*)]"/>

<description>Strimp Empty Values [Modify]</description>
    <if-operation mode="case" op="equal">modify</if-operation>
    <if-operation mode="case" op="equal">sync</if-operation>
    <do-strip-xpath expression="modify-attr/add-value[value='']"/>
    <do-strip-xpath expression="modify-attr[not(*)]"/>

Although there is probably a more efficient way to do this, it does work well.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.
Categories: Uncategorized

Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment.  It just worked for at least one person, and perhaps it will be useful for you too.  Be sure to test in a non-production environment.

Leave a Reply

No Comments
By: descent
Nov 14, 2007
6:33 am
Active Directory Automation Cloud Computing Cloud Security Configuration Customizing Data Breach DirXML Drivers End User Management Identity Manager Importing-Exporting / ICE/ LDIF Intelligent Workload Management Knowledge Depot LDAP Migrating from Windows XP or 2003 to SUSE Linux Monitoring Open Enterprise Server Passwords Reporting Secure Access Sentinel Supported Troubleshooting Workflow