Here are the records for which you can set up search filters:
• | Purchase orders |
• | Purchase requests |
• | Statements |
• | Vouchers |
• | Vendors |
When you set up search filters, you can enable any of the search filters that Horizon delivers, change a delivered search filter to meet your library needs, or create your own search filters by copying existing ones and enable them.
After you enable a search filter for a record type (such as purchase orders), Horizon adds a “Search Filter” list to the related Compound Search window. (For example, if you enable search filters only for POs, then Horizon adds a “Search Filter” list only to the Compound Search window for the “Find PO by Header” process.) From this window, you can choose an enabled search filter by which to limit search results.
Here is an example of a Compound Search window for the “Find PO by Header” process:
Horizon uses these pieces to construct a search filter, of which you should be aware:
• | Columns from a Horizon table or SQL view |
• | SQL query string |
• | Your search criteria |
Here is how Horizon uses the table or SQL view name and the query string:
SELECT a list of columns FROM table or SQL view name WHERE search criteria produced by the search involved AND Query String
From this depiction, you can see that Horizon must know the table or SQL view name before the searching even begins. This way, Horizon produces a search filter for that particular search. Because of this complex combination of knowing the correct Horizon table name and SQL query string, you should create a search filter by copying an existing one. This way, you should not typically have a problem discovering the table or SQL view name, or modifying parts of an existing query string.
This section explains these topics:
• | Delivered Search Filters |
• | Enabling or Disabling a Search Filter |
• | Editing an Existing Search Filter or Creating Your Own Search Filter |
• | Deleting a Search Filter |
© 1998-2017 Sirsi Corporation