Lookup definitions

Lookup definitions for SQL server interface:

Lookup definitions for Native web service definitions:

Once the data source has been defined in External datasources and the data source setup has been done as per the previous section, how to apply the data retrieved by that look up needs to be defined using Lookup definitions. The data sources defined in External datasources will automatically appear in the drop down list in the top right hand corner of the “Lookup definitions” screen (that can be found at System>Lookups menu>Lookup definitions), as shown in the screen prints above.

For each data source, the “insert new record” line can be used to add definitions for each of the different types of Lookups that will be able to be used with that data source.

There is no escaping the fact that an IT action is happening here and so the RefTracker “Lookup definitions” page should be completed by someone who understands the layout of the data source being looked up, the data that will be retrieved and how that data will be used in RefTracker – and that will generally be an IT person such as a DBA or programmer. Your RefTracker support person will be pleased to offer them guidance.

A Lookup definition defines the SQL query, or the web service request, that will be used to retrieve data from the external data source, the fields that will be retrieved from the external data source using that query, and how those fields are mapped to RefTracker fields. In other words, the Lookup defines the data that will be retrieved, and where that data should be stored in RefTracker. You can define as many Lookups as you need. The same Lookup will often be used in multiple forms.

Ideally, a Lookup should define all of the relevant data that can be retrieved for this type of Lookup, as not all of the retrieved data has to be saved in the RefTracker Request form each time this Lookup is used.