Filtering a GetMetadataObjects Request

Understanding Concatenated Association Paths

An <XMLSELECT> search string that includes concatenated AssociationPath criteria must specify an association name that is valid for the Object component in each AssociationPath.

If Object is a metadata type, then all association paths must begin with an association name that is valid for that metadata type.
If Object is an *, then each association path must begin with an association name that is valid for the metadata type specified in the TYPE parameter.
If Object is an * and the OMI_INCLUDE_SUBTYPES flag is set, then each association path must begin with an association name that is valid for the metadata type specified in the TYPE parameter or one of its subtypes.

The AssociationPath components are joined by an implied AND operator. Therefore, only objects that meet the criteria in the combined AssociationPath components will be selected. When the OMI_INCLUDE_SUBTYPES flag is set, only objects that have all of the specified attribute names are tested for a match.

Example 1:

	Object 1 and Object 2 are subtypes of *. Object 1 has valid associations to associationname1 and associationname2. Object 2 has valid associations to associationname3 and associationname4.
	Query: search="*[associationname1/object][associationname2/object]" Result: Only Object 1 is returned.
	Query: search="*[associationname3/object][associationname4/object]" Result: Only Object 2 is returned.
	Query: search="*[associationname1/object][associationname4/object]" Result: Neither object is returned.

Example 2:

Object 1 and Object 2 are subtypes of *. Object 1 has valid associations to associationname1, associationname2, and associationname3. Object 2 has valid associations to associationname2, associationname3, and associationname4.

Query:

search="*[associationname2/object][associationname3/object]"

Result: Selects Object 1 and Object 2.

Top of Page