Skip to end of metadata
Go to start of metadata

Look Up Tanımları



Look up feature of the column; allows the values to be entered in the fields to be selected from a list.

(info) If a drop-down list or a text-drop-down list is to be used in the form or query editors, the lookup feature of the column must be activated and its related properties set. 



Netigma Loop Up Data Field


Look Up Features


  • 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 Displayed Column Name properties. On the screen, the DEED_NEI_NAME 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 DEED_NEI_NAME 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 in which values to be displayed in the Lookup control drop-down list will be retrieved.

    The use of unified space is also possible in this section. If multiple column values are '||' Separator with separator.

    For example, for PostgreSQL: name || '/' || When used in parcel form, display in the form of 100/8 is provided. The same view is provided for SQL Server when the name + '-' + parse statement is used.


  • Sorting Column Name  

    It specifies according to which column the lookup values are to be sorted. 


  • Additional Criteria   

    This feature is used in the lookup table to provide additionalfiltering for future values. While a fixed criteria such as COLUMN_A = 2 can be added, it supports parametric usage such as OBJECTID = {USER @ PROVINCE_ID}.  More than one criteria can be added, subject to 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.  For parameter list that can be used with extra criteria. See