Hi, I am in a working with FIM and installed a box with FIM RC1. Using sets I am unable to rebuild my environment because of two changes from ILM2 RC0. 1. Contains operator doesn´t appear as an option when attribute is chosen at < Click to select attribute> --- STEPS TO REPRODUCE ---Opens or create a Set Choose Criteria based members tab Select users that match all of the following conditions < Click to select attribute> is <Click to select value> At < Click to select attribute> choose department attribute Replace is operator for other operator then Contains doesn´t appear as an option Q1 In which condition contains operator can be used, because it appears in the list only when no attribute is chosen yet.? 2. Non-indexed attributes doesn´t appear in the user´s attributes list I created a new attribute as text and non-indexed, but it is not displayed in the list of attributes for user resource This attribute is a long text field (100 to 1000 chars), that I have to look for specific string and it could be in any position inside attribute. The attribute is included in the filter scope - Administrator Filter permissions. --- STEPS TO REPRODUCE --- Opens or create a Set Choose Criteria based members tab Select users that match all of the following conditions < Click to select attribute> is <Click to select value> < Click to select attribute> in this list the created attribute is not displayed. Q2. Am I missing some filter or MPR to enable? ThksEduardo VelezConsultantMaint Cia Ltda.Sistemas

Hi Eduardo,In RC1 text attributes cannot be used in xpath predicate conditions in query or set filters. Also, the contains() string function is no longer supported in set filters. - Nima

thanks for your clarification Nima.Thks Eduardo Velez Consultant Maint Cia Ltda.

No problem. Given the title of this thread, I want to take the opportunity to enumerate the other changes in sets usage, relative to RC0. Here is a list of functionality that is no longer supported in RC1:1. The filter /* is not supported. In other words, you cannot create another instance of the "all objects" set that already exists by default.2. The contains() string xpath function is not longer available in sets. Starts-with and ends-with are still available as functions to use.3. Double negation is not supported in filters. This refers to conditions such as not(Attribute != Value). To workaround this limitation, if needed, simply nest the != condition in a set and identify resources that are members of that set. For example, to identify all users without an AccountName, create the set S1: /Person[AccountName != 'Invalid'] and then create the set S2 of all users not in S1: /Person[ObjectID != /Set[ObjectID = 'S1 ID']/ComputedMember].4. The descendants() and descendant-in xpath functions are no longer available in query or sets.5. You cannot have an equality expression that has ComputedMember as the left term in a set filter. For example, the following filter is not supported in sets: /Set[ComputedMember = 'X'], where X is some resource's ObjectID. Use of ComputedMember as the right hand term in the expression is still supported.6. Text attributes cannot be used in filters. For example, you cannot define a set filter based on the XOML attribute of a WorkflowDefinition.- Nima

Hi Nima, I had posted a question on a different thread and was referred to this one. As descendants and descendant-in functions are not supported, are there any alternatives to it? What approach would you recommend for implementing the requirements I had highlighted in the earlier thread without support of these functions? Thanks & Regards, Jameel Syed Principal Consultant, fimGuru - Your window into simplified identities jameel.syed@fimguru.com - http://www.fimguru.com