What I was hoping to do is set up the feed as a delta so I can see
only changes to Members either added or removed from the
"uniqueMember" attribute. When I set up a delta and set "Unique
Attribute Name" to uniqueMember it reports back CTGDIS838W DELTA: The
Key Attribute 'uniqueMember' countains more than one value.

And if I set "Unique Attribute Name" to $dn it wont show changes I
make and process them. It will just say 2 records processed.
I basically want to just see a list of new and removed members from
this group and work on them each time.

What would be the best way to do this?

I hope there is enough info there.

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:

I seem to have the Delta's working ok, howver I seem to be stuck when
a user is removed from the group. I want to process users who have
been taken out of the group and set an LDAP attribute isMember under
their uid to say false. when anything changes in the group the delta
picks this up and porcesses all members of the group again but passes
over most as they already have isMember set to true. How would you
catch that a user is no longer in the uniqueMembers group and be able
to set isMember to false.

So in your Changelog Iterator you map in the uniqueMembers field,
along with whatever else you are interested in. This component works
by grabbing the LDIF stored in the changelog entry and parsing it,
giving you this high granularity of delta tagging (it's the job of the
LDIF
Parser). If the uniqueMembers att changes, it will be mapped in; if
not,
then it will not be available in the conn Entry for mapping.

Once you have it in your AL, it will likely be tagged as "modify" and
contain values tagged as either "add" or "delete". So if you use code
similar to the above to loop through the values and check the
operation
code, setting isMember as needed.

And I assume isMember is in the User entry, so you use the dn values
in uniqueMembers in order to Update these users.

If you download the FormEntry Connector then you an easily drop
in some simple CSV data into the Raw Data field, attach a CSV Parser
and then turn on the Delta Engine. Now run this simple AL in the
Debugger
(Step - Paused mode) and walk through its execution. If you set a
breakpoint at the After GetNext Hook, you will only ever get there if
the Delta Engine detects a change. And you will see how deletes are
handled after the end of input data is reached.

The FormEntry Connector is enormously handy when doing what-if tests
in TDI. Thanks to L2 guru, Lak Sri, for this baby!
http://www.tdi-users.org/twiki/bin/view/Integrator/FormEntry

...if I understood you correctly :)

-Eddie

Hope this helps,
-Eddie

On Jul 1, 6:24 am, Crul <rudig...@gmail.com> wrote: