Child pages
  • Look Up
Skip to end of metadata
Go to start of metadata

Look Up Definitions


A defined look up feature for a column; allows selection for the values entered to the field from a dropdown list.This page explaines Look up features.



Note that if a drop-down list or a text-drop-down list is used in the form or query editor definitions, then lookup feature of the column must be activated and its related properties should be set. 

Diagram not found. This diagram is linked to a page or attachment that has been deleted.


Lookup Settings


  • Active 

    It specifies whether the control is active or not.  
  • Self Lookup      

    When this option is selected, the name of the current column is automatically given as the value of the Lookup control, Value Column Name, and Display Column Name properties. On the screen, the happines_score column's lookup feature is activated and set to self lookup. In this case, for example, if the drop-down list is used in the form editor, the values in the list will come from the happines_score column itself. 
  • Table Name 

    It specifies the name of the source table from which Lookup data is retrieved. 
  • Value Column Name    

    It specified the value column of the lookup control. (Edit value).
  • Displayed Column Name  

    It specifies the table column that values in the Lookup control drop-down list will be retrieved from it. The use of unified space is also possible in this section. Multiple column values can be separated with '||' separator. For example, for PostgreSQL:
    island || '/' || parcel, provides 100/8 type of view. The same view is provided for SQL Server when island + '-' + parcel statement is used.
  • Sort Column Name  

    It specifies according to which column, the lookup values should be sorted. 
  • Extra Criteria   

    This feature is used to provide additional filtering for the values comes with look up. It can be used to add a fixed criteria such as COLUMN_A = 2. Beside fixed criteria, this feature supports parametric usage, for example OBJECTID = {USER @ PROVINCE_ID}.  More than one criteria can be added as they are consistent with the SQL query rules.  Such as COLUMN_A = 2 AND OBJECTID = {USER@PROVINCE_ID}. Because the parameters are case sensitive, this parameter should be carefully written.  OBJECTID = {user @ PROVINCE_ID} is an incorrect usage.  To check parameter list that can be used with extra criteria see here.