Use Dataset Index and Header Rules to change the search criteria for and displayed disambiguation information for dataset records, respectively.
These rules impact the Omnisearch and form autosuggest lists. By default, users can find dataset records by their:
Name
Key
Users may want to make dataset records searchable by values, in addition to showing information for other values. Users can customize this search using a dataset index/header rule. For instance, the above example demonstrates how Slate can show additional attributes about the dataset record, like its location and former name (which is a custom field).
The index/header information also appears when users click "Continued..." in an autosuggest list. The information is displayed in the "data" column:
Creating the rule
Go to Database → Rules.
Click New Rule.
Configure the following settings:
Name: Enter a name for the rule.
Base: Select the Configurable Joins option that corresponds to the dataset you are building the rule for.
Type: Index/Header
Folder: Select a folder for the rule, or select Other and enter a name to create a new one.
Priority: Enter a priority value, like
1, if this is your only dataset index/header rule.Status: Preview
Click Save.
Set the Action setting to Replace Values from Formula.
Configuring the rule
In the Action section, your next steps are to add one or more exports that will be used to search records by, and then reference them in the Formula setting. Optionally, you can add filters to your rule if some records should have different index criteria than others (this is not common).
We've outlined an example below for organization records.
Organization Record Example
In this example, we are looking to:
Show address information. If the organization is in the United States, we want to output its city and state. If the organization is not in the United States, we want to output its city and country.
Show its former name. We've created an organization-scoped field that allows us to enter the former name of an institution. By showing this, users can more easily find their school. Instead of using a field for storing an organization's former name, you can also store and use something like its aliases; for instance, allowing users to find George Washington University by storing "George Washington, GW, GWU" in this field
Join from "Organization" to "Address by Rank Overall" and enter "1" for the "Rank" setting. This will grab the overall rank 1 address for the dataset record.
Add a subquery export.
Specify a "Name", like "Index and Header".
Select the "Output" setting of "Concatenate".
Add the "City" export from the "Address by Rank Overall" join.
We want to output the address' state if it is in the United States; otherwise, we want to output the country. To do that we:
Add a subquery export that uses (a) the "Region" export and (b) the "Country" filter set to IN "United States". Slate will only return a value in this subquery export if the address is in the United States.
Ensure that you have entered ", " as the export separator. This causes your chosen separator (in this case, a comma follow by a space) to dynamically appear after each export, if there is an export that follows it.
Though uncommon, you may want to output a new line that contains the former name of an organization, if the organization has one. In our example, we are storing the former name of a school using a custom organization-scoped field. To do that, we must:
Add a subquery export
Add a literal export with the "Literal" setting of "\n" for a new line
Add a literal export with the "Name" and "Literal" settings of "Former Name: "
Add an export for the former name
Add a subquery filter with (a) the "Aggregate" setting of "Exists" and (b) the former name export. Slate will only return a value in this subquery export if the organization record has a value in the former name field
Reference the Index and Header subquery export in the formula.
Save the rule.
Activating the rule
Activate the rule.








