A few weeks ago—before upgrading to SailPoint IdentityIQ 8.4—this exact same filter produced correct results. What’s particularly strange is that the problem only occurs when the application name is “Active Directory”. If I use any other application name, the filter works without issues.
To rule out UI-related problems, I also tried replicating the query using QueryOptions within a rule, but I’m getting the same outcome: 0 identities found*.*
Has anyone else experienced something similar after upgrading to 8.4?
Or could this be expected behavior or a configuration change I might be missing?
@angelborrego Just for the testing, could you please try updating the appname from Active Directory to something else like AD and see if it works or not.
Also, I tried below code and is working for me:
QueryOptions qo = new QueryOptions();
Filter f1 = Filter.eq("links.application.name", "PRISM");
qo.addFilter(f1);
return context.countObjects(Identity.class, qo);
Is this happening in production environment where you might have lot of accounts across multiple application.
I generally dont use negative condition since they dont perform efficiently on DB query side.
When you say the same method works for other application other than “Active Directory” do you see any lag in response when you run it for other app Vs “Active Directory” (just suspecting if its timing out).
