Navigation:  How To > How to Configure... >

Lookups

Previous pageReturn to chapter overviewNext page

This chapter will describe how to configure lookups for WebOffice 10.8 SP2. 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.

 

Feature class containing the attribute field "Category" with key values

Feature class containing the attribute field "Category" with key values

 

Table containing the key value and language specific translations

Table containing the key value and language specific translations

 

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

Note: See chapter DB Connections for configuration details.

 

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

Note: See chapter Tables for configuration details.

 

Configure a table query with a search field pointing to the lookup ID field

Configure a table query with a search field pointing to the lookup 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"

Note: See chapter Layer Queries for configuration details or use the WebOffice author wizard Create Layer Query.

 

Configure a layer query that uses the attribute field both as search field and result field

Configure a layer query that uses the attribute field both as search field and result field

 

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

Note: See chapter Lookup for configuration details.

 

Configure a lookup element that replaces the ID value with language specific values

Configure a lookup element that replaces the ID value with language specific values

 

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.

 

Replaced ID values with language specific values in the WebOffice html client

Replaced ID values with language specific values in the WebOffice html client