Difference between revisions of "Record Locators"

From LongJump Support Wiki
imported>Aeric
imported>Aeric
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
'''Designer > Data > Objects > {object} > [Record Locators]'''
'''Designer > Objects > {object} > [Record Locators]'''


The Record Locator option (available for {{type|}}s only) provides the ability to define three types of fields by which you can locate records in objects.
The Record Locator option (available for {{type|}}s only) provides the ability to define three types of fields by which you can locate records in objects.
Line 13: Line 13:


The fields selected in this option appear as columns in a [[Lookup Window]] when the user is selecting a record, and in a grid display of [[Search]] results. In both cases, they help the user to select the record(s) of interest.
The fields selected in this option appear as columns in a [[Lookup Window]] when the user is selecting a record, and in a grid display of [[Search]] results. In both cases, they help the user to select the record(s) of interest.
This value is also returned as a record's "displayValue" attribute in [[REST API]]s.


=== Record Identifier Fields ===
=== Record Identifier Fields ===
Line 20: Line 22:


This option defines the field(s) in a record that are used by the search process. When choosing fields as search fields, it is good practice to choose fields likely to contain unique information and to exclude large text fields, which can slow the process.
This option defines the field(s) in a record that are used by the search process. When choosing fields as search fields, it is good practice to choose fields likely to contain unique information and to exclude large text fields, which can slow the process.
The first 1024 characters of the concatenated field value(s) are used when searching for a match. For example, if a Text field of 30 characters and a Text Area field of 2000 characters are designated, the search examines the concatenation of 30 characters from the Text field and the first 994 characters from the Text Area.
==== Search Field Example ====


For example, in a ''Parts Inventory'' object, the most likely fields to search are:
For example, in a ''Parts Inventory'' object, the most likely fields to search are:
:*part number
:* <tt>part number</tt>
:*part name
:* <tt>part name</tt>
 
With that specification, even though fields <tt>part_description</tt> and <tt>price</tt> exist, they would not be "searchable".
 
==== Eligible Search Fields ====
In general, fields that can be used as record identifiers resolve to a single alphanumeric value.


Although other fields are available, these fields, for example, would not be "searchable":
One [[Lookup]] field may be specified.
:*part description
:*quantity
:*price


The value(s) in the search field(s) will be used for a maximum of 1024 characters when searching for a match. For example, if two fields are designated as search fields, a Text field of 30 characters and a Text Area field of 2000 characters, the values used in the search will be the concatenation of the 30 characters from the Text field with the first 994 characters in the Text Area field.
These fields cannot be used:
{|
|
:* File
:* Image
:* Checkbox
|
:* Custom Control
:* Rollup Summary
|}


==Updating Record Locators==
==Updating Record Locators==
Line 36: Line 53:
To update an object's record locators:
To update an object's record locators:


#Click '''Designer > Data > Objects > {object}'''
#Click '''Designer > Objects > {object}'''
#Click the '''[Record Locators]''' button
#Click the '''[Record Locators]''' button
#Select the fields you want to use as Lookup and Search Results Fields in the Available column, and click the right-arrow button to move the field(s) into the Selected list. Use the up- and down-arrow buttons to arrange the order in which they appear in the Lookup window (from left to right). These are the columns that will appear in the Lookup window. The name field appears as the default column, which you can keep or remove.
#Select the fields you want to use as Lookup and Search Results Fields in the Available column, and click the right-arrow button to move the field(s) into the Selected list. Use the up- and down-arrow buttons to arrange the order in which they appear in the Lookup window (from left to right). These are the columns that will appear in the Lookup window. The name field appears as the default column, which you can keep or remove.

Latest revision as of 23:45, 31 August 2012

Designer > Objects > {object} > [Record Locators]

The Record Locator option (available for Custom Objects only) provides the ability to define three types of fields by which you can locate records in objects.

As a good practice, Record Locator fields should always have a value; they should never be empty.

Kinds of Record Locators

Lookup and Search Results Fields

The fields selected in this option appear as columns in a Lookup Window when the user is selecting a record, and in a grid display of Search results. In both cases, they help the user to select the record(s) of interest.

This value is also returned as a record's "displayValue" attribute in REST APIs.

Record Identifier Fields

Designer > Objects > {object} > [Record Locators] > Record Identifier Fields

A Record Identifier (also known as a "record name") consists of one or more fields that are displayed when a record has been selected. (When multiple fields are specified, their values are separated by hyphens and displayed as the value of a Lookup field.)

About Record Identifiers

Ideally, a Record Identifier unique label that distinguishes one record from another (although it need not be). These labels can be seen in Views and Records. If the App Center is not enabled, then the record_id field is the only field used for a Record Identifier. Otherwise:

When a new object is created, the first three fields defined in the object are used to form the default Record Identifier. The Record Identifier can be changed at any time.

Thumbsup.gif

Tip: To ensure that the record identifier is unique, use it to define a Unique Key Index.

Example

In this example, the Customer object specifies the customer_name field as the Record Identifier. When the customer has been selected in a Lookup, the customer_name field is displayed to indicate which record was chosen.

RecordIdentifierFields.png

Eligible Record Identifier Fields

In general, fields that are available for use as record identifiers resolve to a single alphanumeric value of moderate size.

One Lookup field may be specified.

These fields cannot be used:

  • File
  • Image
  • Text Area
  • Custom Control
  • Url
  • Rich Text Area

Search Fields

This option defines the field(s) in a record that are used by the search process. When choosing fields as search fields, it is good practice to choose fields likely to contain unique information and to exclude large text fields, which can slow the process.

The first 1024 characters of the concatenated field value(s) are used when searching for a match. For example, if a Text field of 30 characters and a Text Area field of 2000 characters are designated, the search examines the concatenation of 30 characters from the Text field and the first 994 characters from the Text Area.

Search Field Example

For example, in a Parts Inventory object, the most likely fields to search are:

  • part number
  • part name

With that specification, even though fields part_description and price exist, they would not be "searchable".

Eligible Search Fields

In general, fields that can be used as record identifiers resolve to a single alphanumeric value.

One Lookup field may be specified.

These fields cannot be used:

  • File
  • Image
  • Checkbox
  • Custom Control
  • Rollup Summary

Updating Record Locators

To update an object's record locators:

  1. Click Designer > Objects > {object}
  2. Click the [Record Locators] button
  3. Select the fields you want to use as Lookup and Search Results Fields in the Available column, and click the right-arrow button to move the field(s) into the Selected list. Use the up- and down-arrow buttons to arrange the order in which they appear in the Lookup window (from left to right). These are the columns that will appear in the Lookup window. The name field appears as the default column, which you can keep or remove.
  4. Select the fields(s) you want to serve as Record Identifier Fields, and move them to the Selected list. These are the fields through which you can link objects together. You can keep or remove the default field.
  5. Select the field(s) you want to use as Search fields, and move them to the Selected list. You can keep or remove the default field.
  6. Click [Save].
    The fields you selected are shown.
Recordlocators-edit.gif