Deprecation of Search Filter API
As of the 2011 release, SDL Tridion uses the Content Broker Query API for search filtering functionality . Before 2011, Content Delivery offered a separate API for this in Tridion.ContentDelivery.DynamicContent.Filters.
The old Search Filter API still exists, but is deprecated. However, you may wish to migrate your Search Filter code to new Content Broker Query code for the following reasons:
- The Search Filter API may no longer be supported in the next release of SDL Tridion.
- The Broker Query API for filtering offers new functionality for querying custom metadata easily.
To perform such a migration, you will need to rewrite your filtering code. The Content Broker Query classes are in one of the following locations:
- .NET: Tridion.ContentDelivery.DynamicContent.Query
- Java: com.tridion.broker.querying
The following list provides an overview of the Content Broker Query classes you should use and their old Search Filter equivalents:
- The Broker Query class
ItemCreationDateCriteriareplaces the Search Filter callQuery.AddCriteria(creationdate, ...) - The Broker Query class
ItemModificationDateCriteriareplaces the Search Filter callQuery.AddCriteria(modifieddate, ...) - The Broker Query class
ItemInitialPublishDateCriteriareplaces the Search Filter callQuery.AddCriteria(initialpublishdate, ...) - The Broker Query class
CustomMetaKeyCriteriareplaces the Search Filter callQuery.AddCustomMetaQuery("KEY_NAME") - The Broker Query class
CustomMetaValueCriteriareplaces the Search Filter callQuery.AddCustomMetaQuery("KEY_NAME=VALUE")
For more detailed information on the Content Broker Query API, refer to the implementation topic about Dynamic content querying and filtering.