Lookup Sets - field descriptions
Lookup tab
Use this tab to customize the data columns for Lookups, Views, Search Results tabs (for search objects) and References tabs.
- Auto Start
-
Should a lookup run a search even if the user has not yet had a chance to enter a search term?
-
Yes - Search immediately with an empty search term.
-
No - The search does not run until the user has a chance to enter a search term.
-
- Column Data
-
Use along with Column Pivot entry for pivoted Search Results views. Leave blank for a non-pivoted view.
For a pivoted view, this value specifies the data that will display in the results. This data will appear under the column caption specified by the Column Pivot column.
In this
SELECT
statement, there are five columns (0 to 4). The column data,tp.pvalue
, is column 4. Therefore, you would enter 4 in Column data for this example.SELECT f.formula_code, f.version,f.description, tp.param_code, tp.pvalue
The Column Data field supports a semi-colon delimited list of data column numbers, instead of just a single column number. Valid values are blank, a positive integer value, or a list of positive integer values.
- Column Desc
-
Enter the column number containing the description of the record being displayed.
- Column Keys
-
Specify the column number containing the key to the records being displayed. This information is used for drilling down to the record.
In views and search result displays, use column 2 as the first column to display data.
You can enter a:- Single number such as 3.
-
More than two numbers such as:2~3~4 (which indicate that the values are derived from column 2, column 3, and column 4).
-
An object with a version number would be two numbers separated by a semi-colon. For example:2;3
Because there are no line numbers in lookups, you can use the first column, normally used for line numbers, to display data.
When using Column Keys, be sure to use .
- Column Pivot
-
Use along with Column Data for Search Results view only. Leave blank for a non-pivoted view.
For a pivoted view, this value specifies the column caption for the results view.
In this
SELECT
statement, there are five columns (0 to 4). If the caption is to be derived from tp.param_code column, enter 3 here. - Custom Mark
-
Optional. Administrators can use this column to mark lookups for their own specific purposes.
- Lookup Code
-
Enter the name of the reference, view, result, or lookup. Names must match the Lookup Set entries.
The ASCII sort order determines the order on the shortcut menu.- References format:
V\Ref<current symbol>#
- Results format:
V\<current symbol>SEARCH#
- View format:
V\<current symbol>#
- Lookup format:
<current symbol>#
Search results views are seen only in the Search symbol form, such as Formula Search.
- References format:
- MULTILINE COLUMNS
-
Pertains only to string values in the View grids (i.e.,
V\<lookup code>
). Specify the column numbers to display in a multi-line format. These column numbers correspond to their positions in the Column Labels field in the Lookup Set > Lookup Language tab. Separate each column number with a semi-colon.Suppose you want the text strings for the Alias 1 and Alias 3 columns to display in a multi-line format. In the Lookup Set > Lookup Language tab, the Alias 1 and Alias 3 columns are in the sixth and eighth position in the Column Labels field. For this example, you must specify 6;8.
- Query Code
-
Enter the name of the query.
For results, include
VIEW
andSEARCH: VIEWITEMSEARCHRESULTS1
.For views, include
VIEW
, the object where the view appears and the name of the viewed object plus a suffix:VIEWITEMFORMULA1
orVIEWITEMSPECIFICATION1
.Include
LOOK
for lookups:FORMULALOOK3
.This column is not used for References.
- Search Query Code
-
Use this column to configure saved search codes in lookups. Include search and lookup in the syntax of the query.
- Set Query Code
-
Use this column to include sets in Lookups. Include “set” and “lookup” in the syntax of the query.
- Start Col Type
-
String or numeric type for the key. This information is required by Optiva for constructing SQL statements correctly.
-
0 = a string type field, like a code. Strings require quotation marks (“) in the SQL statement.
-
1 = a numeric type field, such as Workflow ID. Numerics do not require quotation marks (“) in the SQL statement.
-
- View Symbol
-
Enter the name of the object type being referenced to enable the user to look up an object in a view, reference, or search result.
The View Symbol must be valid. Exceptions are company types of customer or vendor.
The Optiva administrator may leave the View Symbol blank to disable and functionality on Views.
Lookup Language tab
Here, you define the display name used in the view or reference filter list and the captions for the results columns. These labels are language specific.
- Column Labels
-
Enter the text that will appear in the column headings.
Use semi-colons to separate the list.
For example: Formula Code;Version;Description
For lookups, use this column with the Line Label column.
The number of semi-colon delimited values must match the number of columns in the custom query. (Blank labels count, like One;Two;;Three;;;Four.)
- Column Widths
Use with Column Labels. Enter the width of the columns.
in the table. Use semi-colons to separate the list.
For example: 10;20;10;40
Displays for views and results starting with the second column. Start the column width list with a 0 to ignore the first column. For example: 0;20;10;40.
The number of semi-colon delimited values must match the number of columns in the custom query.
This only applies the first time an user goes to a lookup. In subsequent trips, it defaults to the size that the user has resized the column width to.- Language Code
-
Enter the language code you require for language sensitive entries, such as column headings.
- Line Label
-
Enter the text for labeling the categories for sorting the lookup objects. For example, Formula by Keys or Formula by Description.
- Lookup Code
-
Enter the names of the references, views, search results, or displays that are available. Use one row for each. Names must match the entries in the Lookups tab.
- Lookup Sequence
This column controls the order in which Lookups, Reference types, and Report View titles will display in the References and Reports tabs.
When this column is set to 0, the order will be alphabetical. For example, select your formula and go to the References tab. The default order should be: Customers, Formulas, Ingredient Statements, Programs, Specifications, Vendors.
Assigning numerical values to the Lookup Sequence column allows you to change the display order. For example, you can change the formula’s Reference tab display order to show the section titles in this sequence: Programs, Specifications, Vendors, Customers, Formulas, Ingredient Statements.- Title
-
Enter the text that will appear on the shortcut menu, drop-down list, or lookup dialog title bar to indicate the references, results, views, or lookups that are available.
-
References example: Specifications, Vendors,Customers
- Lookups example: Formulas by Formulator
-
Results example: Summary Results, Detail Results, Results with TP Data, Results with Current TP Data
- Views example: Items
-
Lookup Set tab
This tab references the columns in the Lookups and Lookup Language tabs.
- Access Security
-
Enter the level of security access that corresponds to the lookup code.
- Lookup Code
-
Enter the names of all available references, views, and lookups. Use one row for each value. Names must match the entries in the Lookup tab.
- Set Code
-
Enter the name of the object being viewed.
The set code values can be:
(SYMBOL)
or Lookups,V(SYMBOL)
for views, andV\REF(SYMBOL)
for references.
Assigning set views to views and references
Using the Lookup Set > Filter
tab, you can assign set codes to views and references in the Lookup Set
form. This tab is displayed only for Lookup Sets that have the
V\
and V\REF
prefix.
Set code filters are optional. They restrict the list of views that are displayed in the Reports tab of the business object and the list of reference choices that are displayed in the References tab of the business object.
For more information, see the Infor PLM for Process Application Configuration Guide.