If Attribute1 is a reference attribute, which I thought you were saying it is, then the default criteria in the Set builder are "in", "is", "is not" and "not in". There is no "contains". So I guess I'm not following you...http://www.wapshere.com/missmiis

Thanks Carol, Attribute1 is a multivalued referential attribute bound to User. Attribute1 points to objects of type Resource1 (custom resource type). The first set (Set1)is a set of Resource1 type objects and is built by using a condition for an attribute of Resource1. I have to built a set of Users that in Attribute1 have at least one object of Set1. Select user that match all of the following conditions: Attribute1 contains/not contains ..... Attribute1 is a multivalued reference attribute. If it was single valued then the default critera in Set builder are "in", "is", "is not" and "not in" as you say, but in my situation default criteria in Set builder are "contains" and '"not contains".

Thank you Carol, The main problem that I have is that when I try to select the users based on the Attribute1, in the set creation form appears only "Attribute1 contains...." and I have to choose a set. But I want only the users that in multivalued referential Attribute1 have at least one element of Set1, or differently saying I want to select the users that Attribute1 is just a subset of Set1. Do I have to modify an XPath Filter? If yes, which is the correct syntax? Thanks

Hello, I have an issue concerning the Sets in FIM. I have created a criteria-based membership set (Set1) for a custom resource type (Resource1). The User resource has a multivalue reference attribute (Attribute1) that keeps the reference to objects of Resource1 type. I want to built a set that contain the users that in Attribute1 field have at least one of Resource1 objects, contained in Set1. Then I want to build another set that contains the managers of the users in the previous set. Any idea about this? Thanks in advance

The first set should just be a matter of "Attribute1 in Set1". But you won't be able to do the manager set. For some reason Set xpath has been restricted to only allowing ComputedMember and ExplicitMember to be tacked on the end - it doesn't work for Manager or any other reference attribute. ( See http://technet.microsoft.com/en-us/library/ff356871(WS.10).aspx under "Multiple location steps are not supported, except when referencing the membership of a set") http://www.wapshere.com/missmiis