Add standard or custom source objects to a research configuration so AI Relationship Research reads the CRM data that you choose.
| Permission | Required for |
|---|---|
| AI Relationship Research Admin | Access and complete setup flows |
A custom object must have a tab in the App Launcher to be available as a source object.
You add source objects while you configure data sources for a research anchor object. For the full configuration flow, see Configure AI Relationship Research. For an overview of standard and custom source objects, see AI Relationship Research Source Objects.
- From Setup, in the Quick Find box, enter AI Relationship Research, then select AI Relationship Research Setup.
- On the setup landing page, click New AI Relationship Research Configuration or edit an existing configuration.
- Enter a configuration label, description, and then click Save and Continue.
- Select a research anchor object and click Save and Continue.
-
Select data sources, and add standard or custom source objects.
- Click Set Up.
-
Select your data sources.
If you select CRM as a data source for relationship insights, the AI Relationship Research Source Objects section shows the standard source objects delivered for your anchor object. You can also add custom source objects.
-
To include a standard source object, select its checkbox. To exclude one, clear its
checkbox.
Review the Record Count column for each object to judge whether it holds too much data to process well. For guidance, see AI Relationship Research Source Objects.
-
To add a custom source object, click Add Object, and then
select your custom object from the Object list.
A custom object must have a tab in the App Launcher to be available for research. Available objects reflect current permissions and licenses.
-
Under Text Fields to Search, select the fields that contain
relationship-relevant text, such as a description field, and then click
Next.
AI Relationship Research doesn't restrict the field types that you can select, so choose fields that contain meaningful text. Number, phone, and picklist fields rarely add value.
-
Connect the custom object to the anchor object.
- If the custom object is directly related to the anchor object, click Save.
- If the custom object isn't directly related to the anchor object, click
Next. AI Relationship Research shows this message: This
object is not directly related to the Anchor Object. Define the relationship path
to connect them. In the Relationship Path to Anchor field,
enter the path that connects the custom object to the anchor object:
- For a direct, one-hop relationship, enter the API name of the lookup field
that points to the anchor object. For example,
Account__c. - For an indirect, multi-hop relationship, enter the relationship name for each step, ending with the field that reaches the anchor object. For example, to traverse from the custom object to Case and then to Account, enter the Case relationship name followed by the Account lookup.
- For a direct, one-hop relationship, enter the API name of the lookup field
that points to the anchor object. For example,
- Set the access context.
- Save the configuration.
The objects that you enable appear in the source object list and in the configuration summary. For each custom object that you add, use the edit control on its row to update its fields or relationship path, or to remove it.