Link to Selected Fields from Other Table
This data type establishes a single link between two tables, but pulls multiple fields from the source table through that link. This is the most commonly used linked field type because it offers a lot of versatility, and it's easy to extend in the future by adding more fields. Even if you're only linking to a single field, you might use a Link to Selected Fields in case you need to use additional fields from the same source table in the future.
For example, when you select an asset for a service request, the rest of the asset information populates automatically because it's all part of the same Link to Selected Fields.
Each field you select as a link is displayed separately in the form, according to your arrangement on the Layout tab. When you enable multiple values for a Link to Selected Fields, all the data is shown as an embedded table instead. You can select an independent table view and action bar for the embedded table, which means you can show information that isn't included in the fields you selected. In this case, the fields you select are chosen for their use in automation, reporting, the main table view, and in performing searches on the embedded table; otherwise, when it comes to what users actually need to see, you can show any source table information by creating a view in the source table to use in your embedded table.
When you do create an embedded table, it is also important to create an action bar for use in the embedded table. Usually, you don't want to offer as many actions in an embedded table as you do in the source table's main table view, such as Print or Email actions that aren't as useful in the target table's context.
Because enabling multiple values on a linked set forces you to display an embedded table, it's sometimes preferable to use a Link to Single Field from Other Table when you need to enable multiple values. This gives you more display options to choose from. If you need information from multiple fields, but you want to use one of the other display options, consider creating a compound field just for this purpose. For example, Full Name is a compound of the user's First Name and Last Name.
If you want to be able to search on the imported fields and run reports that use them, make sure to select the "Yes, fast search" option in the wizard when you create the field.
Creating a Link to Selected Fields
To create a new Link to Selected Fields:
- Click Setup [Table Name], or go to Setup > Tables, select the table, and click Edit.
- Go to the Fields tab.
- Hover over New and select "Link to selected fields from other table." This opens the wizard on the Table tab.
On the Table tab, you configure the data source for the linked field.
- Select the source table for your linked field. This is the table that holds the data you want to reference in the table you're working in. For example, if you're editing the Contract table to pull in the name of a salesperson, you would select the People table. You can select tables from the current KB, another
Agiloft KB, or an external database table.
- If you select a different source KB, provide the login credentials for a member of the admin group. Then, click Get Tables and select the table you want to use as the source.
- If you select an external database, you must add a database descriptor to the application server. Then, click Get Tables and select the table you want to use as the source. Data pulled from external databases is view-only.
- In the Admin Notes field, enter a brief description of the field and its function, as well as any interaction with other fields or automation that other administrators might need to know.
The Mapping tab holds some of the most important options for configuring the linked field.
- First, select whether to allow the linked field to hold links to multiple records. Links with this option are referred to as "multiple values enabled," and they work differently from links that connect only one record at a time. After you create the field, you won't be able to change this selection. Choose one of the options:
Yes, fast search. If you need to link to multiple records, this is usually the best option. This allows you to use the data from the linked records elsewhere in the target table, and it allows table searches to find the data and include it in search results.
The Maximum Number of External Records to Cache global variable limits the number of external linked field records that can be cached for Fast Search. By default, this global variable is set to 100 records.
- Yes, save space. This option is only used when you want to display many fields from the source records but don't need to search on them. It only links to the data in the source table and doesn't actually copy it to the current table, which can help reduce the size of records.
- No. This limits the field to a single linked record at a time. If the field is editable and a user selects a different record, the previous selection is overwritten and the link is replaced.
- If you chose No, you can also choose whether to allow entries not in the source table. If you select this checkbox, users can enter values that don't match a record in the source table, but there won't be a link since there isn't a record to link to. We refer to non-source values in a linked field as a "loose link" as opposed to a "strict link." If you do allow entries that aren't in the source table, select the Do not update option in the next step.
- Next, select whether to update your linked field when updates are made in the source table. Sometimes you want to keep the linked field in sync, such as keeping a user's contact information up to date. In other cases, you might want to preserve the original value, such as when pulling in the original price paid for an item. Choose one of the options:
- Do not update. After a value is chosen for the linked field, that value is static unless overwritten. This is useful when you want to preserve historical values, such as the price of a product at the time of sale, or when you want to allow entries not in the source table. This is one of the most common options.
- Update matching fields. If you want to allow entries not in the source table, but you do want to update any entries that match the source table, use this option. With this selected, the value is compared to the old value in the source record, and if the old values matched, the new value in the source record is propagated to the value in the linked field.
- Automatically Update in the background. When the linked record is updated, the update is propagated to the linked field. This is one of the most common options. For example, if you link to a Person record and the person's last name is changed, your link is updated to match.
- Automatically Update synchronously. Like the previous option, this keeps the linked field up to date when the source record changes, but in this case, the linked field is updated immediately after the source record is changed, before other rules can run and before control is returned to the user. This option is usually only necessary in complex rule situations, and you should only use it if the option to update in the background does not work correctly for your situation.
The Fields tab displays all the fields in the source table, and here you select the fields to be included from the source table in the linked set.
- If you selected Yes, fast search or Yes, save space to allow linking multiple records, enter a Table Label to display above the embedded table of linked records. If you selected No, you'll be able to relabel each source field you link to.
- For each field you want to include in your link:
- Select the checkbox next to the field. Remember to select at least one unique field.
- In the Field Label column, enter the label you want to show for this field in the target table. For example, you might be linking to the Full Name field in the Person table, but in the target table, this might be relabeled as Assigned To or Salesperson. When linking to multiple fields, you might simply add the source table name to the original field names, such as a linked set of Vendor Name, Vendor Phone, and Vendor Email.
The Permissions tab contains options similar to other wizards, but it also has a specific bulk option to copy permissions from the source table for the linked fields. To view these permissions, click View Permissions.
You also have the option to replace these permissions with those copied from a field in the current table. To copy the permissions from a field in the current table, select it and click Copy Permissions.
The Copy Permissions operation sets the permissions for all of the selected fields. If you want to assign different permissions to some of the fields, or if you've already saved the linked field set and the settings are disabled, go to Setup > Access > Manage Groups and edit the group permissions directly for the affected groups.
When a field is linked to a field in another table, users must be given View Others' permissions to the field in the source table to be able to use the field in the target table. This allows them to view the currently selected value or select a new value for the linked field.
Now, determine how your linked field or fields should behave.
- First, choose how to set the default value, if at all:
- The values from the record(s)... This imports the value from the record in the source table in which a specific field matches a value in the target table. For example, you can have the system choose the correct linked company record based on a match of the Company Name, in the Company table, to the Customer Company in a support case. You can also use a default value for linked fields based on the person who did something, e.g., changed a field value from x to y, created a record, or last modified a record. After you select the two fields you want to use, you can also define logic to apply if there are multiple records that match the criterion.
- Run the [specified] action when the [specified] field is first set or edited. With this option, you can use an Update Fields action to populate the linked field with one or more records based on multiple matching criteria whenever a specific field is changed. For more information, see Populating a Linked Field with a Saved Search.
- The values for the user in the [specified] field of the user who changes the [specified] field. This allows you to pull from a user relationship based on who changed a specific field.
- [Specified record]. Click the search icon to select a record in the source table to use as a template. The linked fields are automatically populated with the values from this record.
None. This leaves the fields empty until a value is selected.
If you're linking to the People table, you can also set the default value to the user who creates or edits the record, the user in the [specified] field of the user who creates or edits the field, or the user who changed the [specified] field.
- Next, choose whether the default values are reapplied. To illustrate these options, imagine a linked field from the Departments table with the default value set to the department whose ID matches the requester's department ID in the current record. Let's see what each option does:
- Once the field has a value, never overwrite it. With this option, after a user updates the field value from the default, the default value is never applied to the record again. For example, using the department example, after a requester is selected, the linked department is set to their department. Afterward, if either the requester or the department is changed, the system simply saves those changes.
- Always reapply the condition to the default value when the record is edited. In this case, when the record is edited, the system sets the default value again. For example, if a different requester is selected, the department updates automatically to that person's department; however, if a user changes just the linked department and saves the record, the department reverts back to the requester's department the next time the record is modified. Because this can seem confusing to users, this option is usually best paired with a view-only field or a field users don't have permission to edit.
- Only update the default value when the source field in the current table changes. This means the default value is only reapplied when an edit in the current table makes an update to the field used to determine the default value. For example, if a user manually changes the department, the new department is saved and the default is not reapplied. However, if a user selects a new requester, which is the source field used to determine the default value, the department is updated to that requester's department.
- In the next section, you can make your linked field required, not required, or required only under certain conditions.
- If your field allows only a single record to be linked, choose whether to require a unique value in your linked field. For example, you might want to make sure each training schedule is assigned to only one user, and each user is assigned to only one training schedule.
- Set Deletable? to Yes or No.
In the next section, you can restrict the source table records that are available for users to link. For example, to choose a vendor location in a contract, you could use a saved search to show only locations in which the Vendor Name matches the Contract Vendor Name.If you want to use a matching field search criterion, select the field in the source table from the field drop-down, choose an operator, and choose variable rather than value from the next drop-down, then click Formula Help. Go to the Parent Field tab to find the field in the current table that you want to match against and to insert it into the search.
- If desired, add visibility conditions to hide or show the field as needed.
- If desired, add conditions to make the field editable or not editable as needed. For example, if you chose the "Always reapply" option in step 2, you might want to make editing conditional.
Now that you've defined the behavior, it's time to determine how the linked field or fields should look. Before getting into the wizard options, take a look at the different outputs you can offer your users.
Display Options Without MVE
This table shows the options for displaying linked fields that only allow single values.
Record Form Appearance
|Hyperlinked box with Lookup|
|Plain text box with Lookup|
|Source field display with lookup|
|View only source field display|
|List of values|
|Hyperlinked view only|
|Plain text view only|
|Auto||Shows a List of values until 50 records exist and then switches to Hyperlinked box with lookup.|
Display Options with MVE
With MVE, a Link to Selected Fields is always displayed as an embedded table. In this case, the only adjustments you need to make to the display are choosing a view and action bar to use in the embedded table.
Setting Display Options
To configure your field display in the wizard:
If your field doesn't have multiple values enabled, select one of the display options for each field you selected on the Mapping tab. You can click the edit icon next to each display option to adjust the length of the field. By default, linked fields are long enough to accommodate the longest possible value from the source record, which often disrupts existing layouts and takes up more space than necessary. Editing the field length here does not affect the field length in the source table. You can also add an instructional pop-up or input instruction for the field here.
Display at least one field in the linked set as a hyperlink so that users can navigate directly to the source record to see more information.
- Choose whether to show values in alphabetical order or the order they were linked in.
- If you are creating a Link to Selected Fields with multiple values enabled:
- Select a source table view to use in the embedded table. In most cases, you'll want a dedicated view to use in embedded tables, with fewer columns that are tailored to the information that is relevant to the target table.
- Select a source table action bar to use in the embedded table. It's almost always best to create an action bar to use in embedded tables to remove irrelevant options, such as print and email.
- If necessary, here you can set the system to check the linked records to see if they're locked for editing, and to display an icon for any records that are currently locked. This is resource-intensive and not usually necessary, so in most cases you should leave this set to No.
- If you're creating a Link to Selected Fields without multiple values enabled:
- Select a source table view to use in the search lookup window. Make sure the view you choose includes enough information for users to identify the correct record to link.
- Define the default search used in the search lookup window. It's helpful to choose String under Default search because a string search finds word fragments as well as whole words, and it's therefore more likely to produce the results that you’re looking for.