Create a reference field

Updated
  • Updated on Jan 14, 2026
  • Published on Dec 9, 2025
  • 2 minute(s) read
  • CC
  • a
 Prev Next

Create a reference field to access data from a related object on a primary record within the Fullcast platform. This allows you to leverage data from related records for your rules and planning without needing to create permanent formula fields or modify the schema in your source system, such as Salesforce.

For instance, your Salesforce Account record (the primary record) connects to a CS Manager User record via a lookup. You may need to use that manager's User Role Name for a Fullcast territory rule, but that specific field does not exist on the Account object in Salesforce.

Determine the field syntax

The specific format you use to retrieve a related record's data is determined by the API name of the lookup field that connects the two objects. Standard fields and custom fields require different syntax.

Standard fields

Standard lookup fields are those built-in to Salesforce by default (AccountId, ParentId, or OwnerId).

  • Identification tip: These API names do not end in __c.

For these fields, you must use the established relationship name (often the name of the related object) rather than the field ID itself.

  • Rule: Do not use __c or __r. Use the standard relationship name.

  • Format: RelationshipName.TargetField

Example: If you are on an Opportunity record and want to pull the Industry from the related Account:

  • Lookup Field: AccountId

  • Relationship Name: Account

  • Target Field: Industry

  • Correct Syntax: Account.Industry

Custom fields

A custom lookup field is one created by your company, and its API name always ends in __c (CS_Manager__c or Person_Lookup__c).

To traverse this relationship, you must change the suffix to denote a reference.

  • Rule: Change the __c suffix to __r.

  • Format: LookupFieldName__r.TargetField

Example: If you are on an Account record and want to pull the User Role Name of a CS Manager:

  • Lookup Field: CS_Manager__c

  • Transformation: Change CS_Manager__c to CS_Manager__r

  • Target Field: UserRole.Name

  • Correct Syntax: CS_Manager__r.UserRole.Names

Add the field in Fullcast

Once you have determined your syntax using the rules above, add the field to your Fullcast object.

  1. Create a new standard or custom field.

  2. Enter Syntax: In the Source Connection tab Column field, paste your syntax (Account.Industry or CS_Manager__r.UserRole.Name) directly into the field instead of selecting from the dropdown.

  3. Configure Settings:

    • Label: Provide a user-friendly name (Account Industry or CS Manager Role).

    • Hierarchy Participation: Select the checkbox to ensure the field is available for use in rules and segmentation logic.

  4. Click Confirm.

  5. Click Save.

Validate the field

The system generally does not validate if a lookup relationship exists at the moment you save the field. To confirm if your syntax is correct, run an import job.

  1. Trigger a migrate all or full import in Fullcast.

  2. Check Results:

    • Success: The import completes without issues, and the field populates with data.

    • Failure: If the import fails (often with a long error message), it indicates the syntax is incorrect. Re-check your spelling and ensure you correctly swapped __c for __r on custom fields.

Advanced examples: chaining relationships

You can pull data through multiple layers of relationships by chaining the names together.

Chaining standard fields

To pull the Parent Account Name onto an Opportunity Line Item:

Opportunity.Account.Parent.Name

Chaining mixed fields

To pull the Type field from an Account, which is related to a custom ARR Object, which is then related to an Opportunity Line Item:

opportunitylineitem.ARR__r.Account.Type