Users can search the Organizations dataset in the Lookup tool or the Omni Search. By default, users can find organization records by searching for record name or location information, with the location information preset/pre-loaded when a database is initially provisioned.
To ensure that a Location is populated for all organization records moving forward (including new additions to your database), you will need to create an Organizations-scoped Index/Header rule to do so.
Creating the rule
To create the display name rule for an organization contact record, perform the following steps:
Select Database from the main navigation.
Under Automations, select Rules.
Select New Rule.
Enter the following configurations:
Name: Give the rule a name (such as "Organizations Index/Header").
Type: Select Configurable Joins.
Category: Select Records.
Base: Select Organizations.
Rule Type: Select Index/Header.
Folder: Place the rule in a folder to keep organization contact rules organized.
Exclusivity Group: Based on the Rule Type selected, the exclusivity setting is automatically enforced and set to Index/Header.
Non-deterministic: Set to Rule is deterministic and has an exclusive priority.
Priority: Enter "1" in this field.
Only one index/header rule should act on a given dataset record at a time. Together the Exclusivity Group and Non-deterministic settings enforce that if multiple rules of this type exist, they will always behave in a mutually-exclusive manner according to the designated priority.
Status: The rule can be set to either Inactive or Preview.
Filters: Leave the Filters section empty so that this rule will affect all Organizations records.
Action: Select an Action of Replace Values from Formula.
Add an overall Join to Address by Rank Overall, with Rank 1 specified – so that only the Overall Rank 1 Address will be returned when referencing that Join. (Refer to the Database Structure & Determination of Table Ranks article to learn how objects such as addresses are ranked within Slate.)
Add a Subquery Export and configure it as follows:
Name: Give the export a simple name (such as “Header”).
Output: Select Concatenate.
Add an Export for address City.
Add Nested Subquery Exports for Region and Country. With this nested approach, it is possible to filter each of these exports to show conditionally if the address Country is or is not in the United States.
Export Separator: Add a comma and single space
,to separate these values.Note that the export separator will be conditionally included only between exports that have a value. The resulting export will be [City], [State OR Country] depending on the record’s address, and potentially less for incomplete organization addresses. Use of the export separator avoids including leading or trailing commas or spaces in the resulting concatenated value.
Select Save.
In the Formula box, type
@to see a dynamic list of available variables. Select the concatenation export built in the previous step, for example@Header. Because the export itself handles the concatenation, the formula serves only to set that value as-is.Save the rule.
.png?sv=2022-11-02&spr=https&st=2026-04-20T19%3A52%3A26Z&se=2026-04-20T20%3A04%3A26Z&sr=c&sp=r&sig=Hd4wavo7pOcVHlADRHCoozxep5ygVISd3clNiBz8Vs4%3D)
Retroactive refresh
The active rule will apply to all eligible dataset records going forward. This won’t, however, apply the changes to organization contact records that already exist in the database. For these, a Retroactive Refresh should be performed to run these records through the rule.
Select New Query from the new display name rule you built.
Add at least one export, and select Run Query.
From the query Output, select Retroactive Refresh, then press Export. A confirmation dialog appears displaying a count of records that will be queued for the rules if this action is taken.
Select Submit, then confirm OK.
After the refresh completes, any organization contact records that meet the new rule criteria will have their index/header updated accordingly to display location information.