Changes

| align="left" | The date range

|-

Reporting searches are typically more complicated than navigation searches since they are intended to return a set of records to populate a report directly without any additional user interaction. These searches can also be saved and run independently of reports and used for browsing data. Data quality analysis searches help identify possible data problems and ensure that programme-specific workflow steps are being followed. These searches can be used to help protect data integrity.

Building searches in IMSMA^NG is a simple three-step process in which information managers determine:

Following these three steps, users can build searches as simple or as complex as the examples below:

When a search is designed, it can be given a name and description and then saved for later use. Saving a search saves the criteria of the search rather than the search results. This means that searches are automatically updated when additional data is added to the system, ensuring that searches return the most up-to-date data. For example, an information manager can build a search called “Open Hazards” that finds 25 hazards with a status of “Open.” If 10 additional hazards are entered into the system with a status of “Open,” the search would find 35 records when it is run again. In this way, searches are dynamically updated as data is added to the system, allowing information managers to assess data trends over time using consistent search criteria. Information managers can also use an existing search as a template to create other searches by using the “Save as” functionality.

* It is recommended that information managers test their SQL in an external SQL editor prior to using it within IMSMA^NG since IMSMA^NG does not provide SQL debugging support.

* Information managers can build complicated queries using SQL and combine them with other criteria, including parameters, to provide virtually unlimited search capabilities to IMSMA^NG users}}

{{HowTo's

}}