Hi,

We have reviewed the XPATH filter limitations as per: http://technet.microsoft.com/en-us/library/ff356871%28WS.10%29.aspx

However, are there any limitations / best practices as to the number of XPATH filters per Set / Group?

For example, we may have a FIM Group that may be made up of 24 different 'OR' XPATH filters - would this be a performance hit on FIM? Is there a limit on these?

Thanks,

SK

• Edited by Shim Kwan Wednesday, December 17, 2014 3:52 AM

Hi Shim,

While there are not perceived limits on the amount of XPATH filters you can define, there is typically an issue when FIM has to calculate the actual members during said configuration change.  For example, after defining the filter for the group and submitting the change, the portal may timeout during processing.  As such, in order to successfully submit a large XPATH filter, you may need to adjust the portal timeout threshold:

http://blogs.msdn.com/b/darrylru/archive/2010/02/02/extending-fim-timeouts.aspx

If your change is successful, then your XPATH filter should be fine.  It will not affect FIM operational, day-to-day performance from what I've seen.

A better way to define complex filters is to combine multiple memberships into one.  For example, in some sets I have defined in the past, I have created three or four separate working sets whose collective membership gathers what is needed.  I then create an "overall" set and perform a collective computed member filter, i.e. /Person[ObjectID = /Group[DisplayName = 'sourceSet']/ComputedMember

Hope that