The unique Attribute should be a key that only appears once
in the input data set, so the $dn is a good choice. Then you
have to map in the members Attribute so that it will be included
in the Delta computation.

For each changed object (e.g. LDAP entry) you get one Entry
returned with the Delta Operation codes that signal what has
changed. At the Entry level this will be an "add", "delete" or
"modify" tag (or "unchanged" if you tell the Delta Engine to
return these too).

For an Entry tagged "modify" you can then check the operation
code of the Attributes. These are also either "add", "delete"
or "modify", and for "modify" there will be tags for individual
values = "add", "delete".

Here is a How-To that describes delta tagging:
http://www.tdi-users.org/twiki/pub/Integrator/HowTo/HowTo_SyncData_6....

To programmatically check this you could script something
like this:

if (work.getOperation() == "modify") {
   attnames = work.getAttributeNames();
   for (name in attnames) {
      att = work.getAttribute(name);
      if (att.getOperation == "modify") {
          for (i = 0; i < att.size(); i++) {
               if (att.getValueOperation(i) == "add" ||
                   att.getValueOperation(i) == "modify") {
                   task.logmsg( "   --> " + name +
                                   "[" + i + "]: " +
                                   att.getValueOperation(i) +
                                   " : " +
                                   att.getValue(i));
               }
          }
      }
   }

-Eddie
On Jun 29, 3:38 am, Crul <rudig...@gmail.com> wrote: