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

# Inspect records

> Check the records and values stored on an object.

export const ThemedImageFrame = ({lightSrc, darkSrc, alt, caption}) => <Frame caption={caption}>
    <div className="block w-full dark:hidden">
      <OptimizedImage className="w-full" src={lightSrc} alt={(alt ?? caption) ?? ""} />
    </div>
    <div className="hidden w-full dark:block">
      <OptimizedImage className="w-full" src={darkSrc} alt={(alt ?? caption) ?? ""} />
    </div>
  </Frame>;

export const PlanAvailability = ({plans}) => <aside aria-label="Plan availability" className="not-prose my-6 flex items-start gap-3 rounded-xl border border-zinc-200 bg-zinc-50 px-4 py-3 text-sm leading-6 text-zinc-700 dark:border-zinc-700 dark:bg-white/5 dark:text-zinc-300">
    <svg aria-hidden="true" width="18" height="18" viewBox="0 0 24 24" fill="none" stroke="currentColor" strokeWidth="1.5" strokeLinecap="round" strokeLinejoin="round" className="mt-1 shrink-0">
      <path d="m12 3 9 5-9 5-9-5 9-5Z" />
      <path d="m3 12 9 5 9-5M3 16l9 5 9-5" />
    </svg>
    <span>Available only on {plans} plans.</span>
  </aside>;

## Overview

<PlanAvailability plans="Business" />

Use the **Records** tab in Data management to check what an integration or API
has stored in an object. This is useful after setting up a custom object, sending
a first batch of data, or investigating an unexpected value in a workflow.

For help loading data into a new object, see
[Connecting data to Unify](/developers/connecting-data).

## Check a record

<Steps>
  <Step title="Open the object's records">
    Open [Settings → Data management](https://app.unifygtm.com/dashboard/settings/data/data-management),
    select the object, and click **Records**. The object's header shows its record
    count and API name.
  </Step>

  <Step title="Choose a record">
    Use **Sort** to find recently updated records, then click a record to open
    its details. Check its record ID and **Last updated at** timestamp to confirm
    you are inspecting the intended record.
  </Step>

  <Step title="Review the stored values">
    Inspect the attribute values in the record details. Compare them with the
    source record, including identifiers and dates. Click **JSON** when a
    developer needs the stored field names and structured values.

    <ThemedImageFrame lightSrc="/images/reference/objects/workspace-record-light.png" darkSrc="/images/reference/objects/workspace-record-dark.png" alt="A synthetic product workspace record showing its identifier, active users, renewal date, and onboarding status." />
  </Step>
</Steps>

## Check a relationship

For a relationship to one record, check the stored reference on that record.
For example, open a subscription to check which company it belongs to.

The record details view does not list the records in a relationship that allows
many. A company's subscriptions can therefore appear empty here even when
subscriptions are linked to it. Check the company reference on the subscription,
or ask your integration owner to look up subscriptions linked to that company
through the API.

## If the result is unexpected

If there are no records, confirm that your integration or API has sent data to
this workspace and the correct object API name. An empty object immediately
after creation is expected.

If a value is missing or incorrect, compare the source payload with the
[attribute definition](/reference/objects/create-attributes) and its
[value type](/reference/objects/value-types). Check whether the write was rejected
because a required value was missing or a unique value already existed.

If a single-record relationship is empty, confirm that the source supplied a
link to the related record. Use the record ID, object API name, and update time
when investigating the write with the developer or integration owner.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.