I have two homePostalAddress (structured) attributes. I want to do
something that would be simple with any other attribute, with a
do-set-dest-attr-value on one using the value from dest-attr of the
other one. But it looks like IDM isn't quite handling the structured
attribute the way I'd like it to, because do-set-dest-attr-value
defaults to "string".

If I try to specify that the do-set-dest-attr-value target is
structured, then I need to provide the strings to fill it in with.
Which, to get those, means that I have to read and parse the dest-attr
(source) structured attribute in to a bunch of local variables or
something, so that I can specify the values in to the destination
strings.

Shouldn't this be easier?

What I want to do:

<rule>
<description>Copy Postal Address</description>
<conditions>
<and/>
</conditions>
<actions>
<do-set-dest-attr-value name="LocalAddress">
<arg-value>
<token-dest-attr name="homePostalAddress"/>
</arg-value>
</do-set-dest-attr-value>
</actions>
</rule>

I know why this doesn't work, but what I want to know is why shouldn't
it work. It'd be a lot easier than the hoops I'm having to jump through
with xpath to get each string value and stick it in the right spot in
the structured attribute.


---------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Novell Support Forums Volunteer SysOp http://forums.novell.com

Please post questions in the newsgroups. No support provided via email.