---
title: "Designate reference proxy fields"
slug: "designating-reference-proxy-fields"
updated: 2026-04-27T19:36:01Z
published: 2026-04-27T19:36:01Z
canonical: "help.quickbase.com/designating-reference-proxy-fields"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.quickbase.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Designate reference proxy fields

Once you've created a [table-to-table relationship](/v1/docs/what-are-table-to-table-relationships), you may find that the [reference field](/v1/docs/what-are-table-to-table-relationships#fields-used-with-relationships) doesn't show the information you want. For example, when you display a record or report, the field may show the Record ID#. You may want to show more meaningful information, such as project name or company.

Numbers may be shown in reference fields because Quickbase typically uses the parent table's key field (such as Record ID#) to link the tables together. But, you don't need to use the reference field in reports and on forms. Instead, Quickbase lets you designate a ***reference proxy field***. Use this feature to specify that another field, containing more user-friendly information, should look and act like the reference field when you create or edit a child record.

For example, instead of **Record ID#**, use the **Company Name** field. You then use this reference proxy field in reports and forms instead of the reference field. You can still use the field to select values from a parent table or to access the parent record.

If you add at least one [lookup](/v1/docs/creating-lookup-fields) field to your table-to-table relationship, then that field is designated as the reference proxy automatically. But you may need to add or change the reference proxy field settings for a table-to-table relationship in your app.

You designate reference proxy fields within the properties of the relationship's reference field, in the child table.

Before you start, the child table needs to include at least one **lookup**field, which includes data from the parent table, or at least one **formula**field, which could also include data from the lookup fields, as these field types are included as choices for the reference field proxy.

> [!NOTE]
> Note: You can create a formula field that combines values from lookup fields, then you can select that formula field as your proxy field. For example, you may want to combine a project manager first name field and a project manager last name field into a single entry.

To designate a reference proxy:

1. [Access the field properties](/v1/docs/change-the-properties-of-a-field-from-a-legacy-form) of the relationship's reference field, either by [editing the relationship](/v1/docs/adding-fields-to-table-to-table-relationships) or opening table settings.
2. In the **Reference field options** section, select the **Proxy field** drop-down and select the field you want. ![Reference field options section showing the Proxy field dropdown](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/refproxy.png)
3. Select **Save** in the upper right to save the field properties.
4. Add the reference proxy field to any additional reports and forms.
5. You may also want to review the [record picker settings](/v1/docs/setting-record-picker-display-fields) for your tables, to customize the values that appear in your reference proxy field.