Syncing only users without "Disabled" in description attribute

I just tested this functionality in my lab and it does work, although it is not as obvious as applying a filter at the Connection level.

This is my test Workflow without a filter:

Here is the filter that I applied:

Here are the expected objects that the filter should apply to:

Here are the results with the filter applied:

So, the filtered value is applied to the "Objects to be updated", but it's not in the "Objects not meeting scope conditions". That is for objects which are filtered out at the Connection level.

Please confirm the expected values and you may see that they are matching the actual numbers being updated.

Thanks so much Terrance for the quick reply Terrance!

This does work for me too. BUT, my requirement is the negative condition (i.e. description DOES NOT contain "go" in your example).

When I try that, it has zero Objects to be updated. Could you please try that in your test environment as see if the behavior is the same for you?

Thanks!

Confirmed, the "Does not contain" filter seems to work just fine as well:

That's interesting!! The only difference between yours and mine is that your source is ARS and mine it's another Active Directory source. Wonder if that's relevant here.

I wouldn't expect it to be.

What version of Quick Connect are you running?

I am testing this in Active Roles Synchronization Service 7.4.1, but they are functionally identical in this respect. However, I can spin up a test lab with your exact Quick Connect version and confirm functionality.

Do you have Active Roles or have you gathered the expected numbers using an LDAP Filter in Active Directory Users and Computers?

We have Quick Connect 5.3.0.457

I just checked with an LDAP filter below and it does work properly.

(&(&(&(objectcategory=person)(objectClass=user)(!(description=*Disabled*))))) 

Quick Connect 5.3.0 is positively ancient by software standards.

Released in August of 2013, and out of support for several years now.

It's entirely possible that there is some known issue that was fixed in the several generations since, although I don't see one from a cursory look.

I strongly suggest upgrading to Quick Connect 5.5 or Quick Connect 6.1 and then testing this functionality again.

Quick Connect 5.3.0 is positively ancient by software standards.

Released in August of 2013, and out of support for several years now.

It's entirely possible that there is some known issue that was fixed in the several generations since, although I don't see one from a cursory look.

I strongly suggest upgrading to Quick Connect 5.5 or Quick Connect 6.1 and then testing this functionality again.

Thanks Terrance! Yes, agreed! But, that's something I cannot change at the moment. I'll try to workaround the issue outside of Quickconnect. Thanks again for your help with testing!

Did you try MY suggestion above?

The connection filtering didn't work either JohnnyQuest! It yielded the same result as the provisioning filter did.

Thanks for letting me know.