This chapter will describe how to configure lookups for WebOffice 10.9 R4. Consider lookups if you want to provide

•support for language specific attributes/fields:
Example: your project supports both English and German language and you got an attribute field Category with values fire department, police and emergency ambulance. If your project is started with the German interface (by adding the parameter &language=de) you want to have the german expressions for these values.

•unique value lists for populating search forms with minimal database usage:
Example: you have a big address table with fields post code, street and house number, you would need to search the whole address table for providing a list of post codes. If you instead use a lookup table for providing the list of post codes you need to search the small lookup table with unique values only.

 

Below you see a table of a feature class that contains an attribute field Category containing key values to distinguish between various types of emergency stations (fire departments, police stations and emergency ambulances). Additionally, there exists a table that contains the language specific translations for these categories. You want to configure a predefined query on attribute field Category but provide a language specific list of names instead of the key values both in the search form and the search result.

 

 

 

First, a database connection to the database containing your lookup table has to be established in WebOffice author.

 

 

In the next step configure a table query with a search field pointing to the ID field.

 

 

 

Now you can create a layer query with

•a search field list containing the field Category"

•a predefined query using the search field Category"

•a result view containing the result field Category"

 

 

 

At this point only ID values will be displayed both in the search form and the search result. Therefore, right-click on the query element an add a list of lookup definitions together with a lookup element.

For this lookup element choose:

•the attribute field of your feature class that is used as search and result field

•the lookup ID field of your lookup table

•the language specific fields for the respective languages

 

 

 

With this configuration it is possible to replace the ID values and show language specific value both in the search form and the search result.