Modify set xpath query request failed with multi-value reference attribute
I have a custom multivalue reference attribute on my User schema (call it UserFolders) which contains a subset of UniqueIdentifiers which are the keys for a custom object - call it "UserFolder". The schema of the UserFolder object contains a FolderID
and a UserID (foreign keys). I need to define a group of all the users who are linked to folders by the presence of a UserFolder object.
A search scope that would return the set of users for a specific folder would look like this (and I wouldn't need to use the UserFolders attribute at all):
/Person[ObjectID = /UserFolder[FolderID = 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx']/UserID]
However, going by the rules stated in the Unsupported filter definitions section of the FIM documentation, I always knew that "Multiple location steps are
not supported, except when referencing the membership of a set". So looking at this differently, consider the following alternative using the UserFolders attribute bound to the User:
/Person[UserFolders = /UserFolders[FolderID = 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx')]]
Now both the queries above return the same results in a search scope, and option #1 is known to be unsupported, but I can't find a reason anywhere why option #2 is unsupported. Can anyone explain this for me, or is this supposed to work???
I don't want to have to resort to creating sets for every variation of /UserFolders[FolderID = 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx')] that I'm going to have because that will bloat the FIM db, but at this stage it's the only way I can get the group criteria
working, i.e.
/Person[UserFolders = /Set[ObjectID='xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx']/ComputedMember]
Thanks in advance.Bob Bradley, www.unifysolutions.net (FIMBob?)
November 29th, 2010 7:04pm