Symptoms

Within the K2 environment, we have a service broker called "AD Service 2".

This service broker has an option to "ResolveNestedGroups".
This works very well when you use the "GetUsersByGroup" on the AD User service object. We then get the users from the group you entered and any users in nested groups.
The filter option (which a picker control on a smartform would add) does NOT work on the users in the nested group.

To reproduce:

1. Create "Group1"
2. Create "Group2"
3. Add user1 to group1.
4. Add user2 to group2.
5. Add group2 to group1.
6. Change the service instance to have "resolveNestedGroups" to "true"
7. Generate a SMO for the AD User service object.
8. Execute the SMO's "GetUsersByGroup" method, providing "Group1" as the group name. You should see user1 and user2 being returned.
9. In the SMO tester, add a filter for the Name property containing "user". This will only return user1, not user2, which should match but due to the fact that it's in a nested group - does not.

 

Diagnoses

See resolution
 

Resolution

This was resolved by linking it to TFS and sending a coldfix.
TFS_492781 - K2 blackpearl 4.6.8
TFS_524886 - K2 blackpearl 4.6.9

Please note after applying the coldfix, the AD Service 2 service instance has new properties in the form of True or False, I set the first 3 options to True and the last option to False to get this working.