nickmo
Posts: 32
Score: 0 Joined: 8/25/2008 Status: offline
|
quote:
ORIGINAL: nbarker Russ Try the following Membership query rule against the Root collection, changing the AA1000a1 and AA1000a2 for the CollectionID of your Sub1 and Sub2 collections (CollectionID can be easily seen on the Properties page of a collection). select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.ResourceId in (select resourceid from sms_cm_res_coll_AA1000a1) or SMS_R_System.ResourceId in (select resourceid from sms_cm_res_coll_AA1000a2) Kandle That is another solution, which I hadn't considered doing it like that. While it does work, it is still a query static data where you have to create a subselect for every [sub] collection. Again, one could as well create a query to return all resources and then filter that through the collection. Do you know of a method where someone could define a parent collection ID, but have it return results for all child [sub] collections?
_____________________________
nick
|