Filter can not be rendered - The filter may be corrupted or unsupported by the Filter Builder
I have created 2 groups using Powershell using below two filters. /Person[(AccountName != '_Invalid_') and (LastName = 'GroupMember1') and (FirstName = 'Test')] /Person[(AccountName != '_Invalid_') and (LastName = 'Raj')] The scripted execute fine, but I'm getting below error when trying to open the group filter from FIM Portal. Anyway it is successfully fetching members. "Sorry, the filter you are trying to display cannot be rendered with the Forefront Identity Manager Filter Builder. The filter may be corrupted or unsupported by the Filter Builder." Please provide suggestions\thoughts to fix this error message. Note:- (AccountName != '_Invalid_') is the syntax used to filter members who have no AccountName. as specified in http://social.technet.microsoft.com/Forums/en-US/ilm2/thread/bd9771c9-63bc-44c7-bd99-d5ea0a20c68b/ and http://msdn.microsoft.com/en-us/library/ff393652.aspxAswathy Raj
June 21st, 2011 12:27pm

Verify that the user account that's using the filter builder has the Filter necessary permissions (separate from MPR Permissions)ex-MSFT developer, now FIM/MIIS/ILM/WPF/Silverlight consultant | http://blog.aesthetixsoftware.com/
Free Windows Admin Tool Kit Click here and download it now
June 21st, 2011 1:06pm

Your filter is too complicated for the UI. See http://social.technet.microsoft.com/Forums/en-US/ilm2/thread/8dd509d2-c80c-4d90-a752-49cfb2f247cb/
June 21st, 2011 3:08pm

Ikrima and Robert both make very good points. However, I don't see those filters as being very complex. So I am going to ask some simple questions: 1) Do your groups have any members in them? 2) Are they the members you expect? If so then Robert's point should be regarded. If not then consider Ikrima's post. Additionally, I must ask if your filter attribute contains all of the surrounding XML. Open the group in advanced view and grab the entire text of the filter attribute and paste it in here. If the text starts with /Person then you are missing the surrounding XML <Filter xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" Dialect="http://schemas.microsoft.com/2006/11/XPathFilterDialect" xmlns="http://schemas.xmlsoap.org/ws/2004/09/enumeration"> /Person[AccountName!='_invalid_' </Filter> Another item to consider is that you can also do a filter to detect presence of a string like so: /Person[Starts-With(AccountName,'%')] The % is a wild card in Starts-With, Ends-With functions. So the above filter will return all person objects that have something in the AccountName attribute. David Lundell, Get your copy of FIM Best Practices Volume 1 http://blog.ilmbestpractices.com/2010/08/book-is-here-fim-best-practices-volume.html
Free Windows Admin Tool Kit Click here and download it now
June 22nd, 2011 2:17am

Well, the filter is not that complex, but the operator != is unknown to UI. If you create filter "AccountName is not _Invalid_" via UI, what it really does is not(AccountName = '_Invalid_'). I think your filter would work, only UI cannot render it. David is right, /Person[Starts-With(AccountName,'%')] would also work and also UI can render it.
June 22nd, 2011 8:40am

Thanks for all your inputs. It passed with using /Person[Starts-With(AccountName,'%')] - Not Null Check on FIM attribute. Once again thanks to all of you.Aswathy Raj
Free Windows Admin Tool Kit Click here and download it now
June 23rd, 2011 11:34am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics