Skip to main content

ObjectTable

A comprehensive guide for using the ObjectTable component from @osdk/react-components.

Prerequisites

Before using ObjectTable, make sure you have completed the library setup described in Prerequisites, including:

  • Installing the required dependencies
  • Wrapping your app with OsdkProvider
  • Adding the CSS imports and configuring @layer order

Table of Contents

Import

import { ObjectTable } from "@osdk/react-components/experimental/object-table";
import type {
ColumnDefinition,
EditFieldConfig,
} from "@osdk/react-components/experimental/object-table";

Basic Usage

About @my/osdk

@my/osdk is a placeholder for your generated SDK package (e.g. @your-app/sdk). Replace it with the actual package name in your project.

Minimal Example

The simplest way to use ObjectTable is with just an object type:

import { Office } from "@my/osdk";
import { ObjectTable } from "@osdk/react-components/experimental/object-table";

function OfficesPage() {
return (
<ObjectTable
objectType={Office}
/>
);
}

This displays all properties of the Office object type in a table with default settings.

With Selection

Add selection mode to enable row selection:

<ObjectTable
objectType={Office}
selectionMode="single" // or "multiple" or "none" (default)
/>;

Props Reference

This table is generated from the ObjectTableProps interface in ObjectTableApi.ts — edit the JSDoc there, not this table. See Column Definitions below for the shape of the columnDefinitions prop.

Type parameters: Q extends ObjectOrInterfaceDefinition, RDPs extends Record<string, SimplePropertyDef> = Record<string, never>, FunctionColumns extends Record<string, QueryDefinition<{}>> = Record<string, never>

NameTypeDescription
objectTypeQRequired. The object or interface type of the object If objectSet is not provided, objects will be fetched based on this type.
objectSetObjectSet<Q>The set of objects to show in the table. If provided, the table fetches through this object set instead of fetching based on objectType. Supported for both object and interface types.

For an interface object set, rows expose the interface's declared properties; the underlying concrete object's non-interface properties are not loaded. Use objectType-based fetching if you need those.
columnDefinitionsArray<ColumnDefinition<Q, RDPs, FunctionColumns>>Ordered list of column definitions to show in the table

If not provided, all of the properties of the object type will be shown in default order.
objectSetOptionsObjectSetOptions<Q>
dedupeIntervalMsnumberMinimum time between fetch requests in milliseconds. Increasing this value reduces redundant network calls when the same data is requested multiple times in quick succession. Defaults to 60_000 1 minute.
streamUpdatesbooleanEnable streaming updates via websocket subscription. When true, the table will automatically update when matching objects are added, updated, or removed in Foundry.

Limitations: streamUpdates cannot be used together with pivotTo or withProperties. The server does not support websocket subscriptions for link-traversal or derived-property queries. Those queries still fetch data normally but won't receive real-time updates. Defaults to false.
pageSizenumberNumber of objects to fetch per page. Defaults to 50.
filterWhereClause<Q, RDPs>The current where clause to filter the objects in the table. If provided, the filter is controlled.
enableColumnConfigbooleanWhether the column configuration dialog for column visibility and ordering is available to the user. Defaults to true.
enableColumnPinningbooleanWhether columns can be pinned by the user. Defaults to true.
enableColumnResizingbooleanWhether columns can be resized by the user. Defaults to true.
onColumnVisibilityChanged(newStates: Array<{ columnId: PropertyKeys<Q> | keyof RDPs | keyof FunctionColumns; isVisible: boolean; }>) => voidCalled when the column visibility or ordering changed.

If provided, the table will allow the user to show/hide columns.
onColumnsPinnedChanged(newStates: Array<{ columnId: PropertyKeys<Q> | keyof RDPs | keyof FunctionColumns; pinned: "left" | "right" | "none"; }>) => voidCalled when the pinned columns change.

If provided, the table will allow the user to pin/unpin columns.
onColumnResize(columnId: PropertyKeys<Q> | keyof RDPs | keyof FunctionColumns, newWidth: number | null) => voidCalled when a column is resized.
onColumnHeaderClick(columnId: PropertyKeys<Q> | keyof RDPs | keyof FunctionColumns) => voidCalled when a column header is clicked.

The columnId matches the locator.id configured on the column definition. The dropdown menu trigger is excluded — clicking the chevron opens the header menu instead of firing this callback.
enableOrderingbooleanWhether the table is sortable by the user. Defaults to true.
defaultOrderByArray<{ property: PropertyKeys<Q> | keyof RDPs; direction: "asc" | "desc"; }>The default order by clause to sort the objects in the table. If provided without orderBy prop, the sorting is uncontrolled. If both orderBy and defaultOrderBy are provided, orderBy takes precedence.
orderByArray<{ property: PropertyKeys<Q> | keyof RDPs; direction: "asc" | "desc"; }>The current order by clause to sort the objects in the table. If provided, the sorting is controlled. If both orderBy and defaultOrderBy are provided, orderBy takes precedence.
onOrderByChanged(newOrderBy: Array<{ property: PropertyKeys<Q> | keyof RDPs; direction: "asc" | "desc"; }>) => voidCalled when the order by clause is changed. Required when sorting is controlled.
selectionMode"single" | "multiple" | "none"Selection mode for the table rows.

If multiple, a checkbox will be shown for each row to allow selecting multiple rows as well as a top-level checkbox in the header to select all rows. Defaults to "none".
selectedRowsPrimaryKeyType<Q>[]The currently selected rows in the table. If provided, the row selection is controlled.
isAllSelectedbooleanIndicates whether all rows are selected in controlled mode. When true, the table will show all rows as selected regardless of the selectedRows array.
onRowSelectionChanged(change: RowSelectionChange<Q, RDPs>) => voidCalled when the row selection changes, with a RowSelectionChange payload describing the new state.
focusedRowPrimaryKeyType<Q> | nullThe primary key of the row to render as visually focused (the "last interacted" row). When provided, focus state is controlled by the caller.

Stored as a primary key rather than a full object so the focus does not go stale when the underlying row data changes.

Pass null to render no row as focused.
onFocusedRowChanged(row: Osdk.Instance<Q, "$allBaseProperties", PropertyKeys<Q>, RDPs> | null) => voidCalled when the focused row changes — fires in both controlled and uncontrolled modes so callers can observe focus without taking it over.
editMode"always" | "manual"Controls the edit mode behavior of the table. - "always": Editable cells are immediately in edit mode on row clicked. - "manual": User can toggle edit mode on/off via the Edit Table button. Defaults to "manual".
showEditFooterbooleanWhether to render the bottom edit footer that hosts the "Edit Table" / "Cancel" / "Submit Edits" buttons and the edit-state indicators (modification count, validation errors). Defaults to true whenever the table has at least one column declared editable (i.e. any column with editable: true or editable: (object) => boolean). When false, the "Edit Table" and "Submit Edits" buttons will not be shown.
onCellValueChanged(info: CellEditInfo<Osdk.Instance<Q, "$allBaseProperties", PropertyKeys<Q>, RDPs>, unknown>) => voidCalled after the value of a cell is edited and committed by the user.
onSubmitEdits(edits: CellEditInfo<Osdk.Instance<Q, "$allBaseProperties", PropertyKeys<Q>, RDPs>, unknown>[]) => Promise<boolean>If provided, the "Submit Edits" button will be shown in the edit footer.
onRowClick(object: Osdk.Instance<Q, "$allBaseProperties", PropertyKeys<Q>, RDPs>) => voidCalled when a row is clicked.
renderCellContextMenu(row: Osdk.Instance<Q, "$allBaseProperties", PropertyKeys<Q>, RDPs>, cellValue: unknown) => React.ReactNodeIf provided, will render this context menu when right clicking on a cell
rowHeightnumberThe height of each row in pixels. Defaults to 40.
renderEmptyState() => React.ReactNodeRender override for the empty state. Called when the table has no rows and no error. When omitted, a default "No Data" indicator is rendered.
getRowAttributes(object: Osdk.Instance<Q, "$allBaseProperties", PropertyKeys<Q>, RDPs>) => Record<string, string | undefined>Returns extra HTML attributes (typically data-*) to apply to each row element. Use this to drive conditional row styling
tableRefReact.Ref<ObjectTableHandle<Q, RDPs>>Imperative handle for programmatic table actions. Pass a ref (useRef<ObjectTableHandle<Q, RDPs>>(null)) to call ObjectTableHandle methods such as ObjectTableHandle.getSnapshot.
classNamestring
labelsPartial<ObjectTableLabels>Overrides for the table's user-facing strings. Provide any subset; unset keys fall back to the built-in English defaults. Use this to localize the table or adjust wording. See ObjectTableLabels. Defaults to undefined (built-in English strings).

Object set options

The objectSetOptions prop combines the table's object set with others before fetching:

Type parameters: Q extends ObjectOrInterfaceDefinition

NameTypeDescription
unionObjectSet<Q>[]Object sets to union with
intersectObjectSet<Q>[]Object sets to intersect with
subtractObjectSet<Q>[]Object sets to subtract from

Column Definitions

Column Definition Structure

Each entry in columnDefinitions is a ColumnDefinition. The locator identifies what the column shows (see Column Locator Types); the remaining fields control appearance and behavior.

Type parameters: Q extends ObjectOrInterfaceDefinition, RDPs extends Record<string, SimplePropertyDef> = Record<string, never>, FunctionColumns extends Record<string, QueryDefinition<{}>> = Record<string, never>

NameTypeDescription
locatorColumnDefinitionLocator<Q, RDPs, FunctionColumns>Required. Defines what the column shows: an object/interface property, a linked object property (derived property), a function column, or a custom column — and carries that locator's configuration.
isVisiblebooleanDefaults to true.
pinned"left" | "right" | "none"Defaults to none.
widthnumber
minWidthnumber
maxWidthnumber
resizableboolean
orderableboolean
renderCell(object: Osdk.Instance<Q, "$allBaseProperties", PropertyKeys<Q>, RDPs>, locator: ColumnDefinitionLocator<Q, RDPs, FunctionColumns>) => React.ReactNodeCustom renderer for the cell value.

Interaction with editable columns: - When editMode: "manual" (default), renderCell is used while the table is read-only (Edit Table button visible) and the editable cell takes over once the user enters edit mode. - When editMode: "always", the editable cell always wins on editable columns and renderCell is ignored — editMode: "always" opts the column into a permanently-editable surface, leaving no read-only state for renderCell to render. Use editMode: "manual" if you need a custom display alongside editing.
columnNamestringIf provided, this will be used in the column header. If both columnName and renderHeader are provided, renderHeader will take precedence in the table header. columnName will still be used in other parts where the column name is displayed.

If not provided, for a property column, the property displayName will be used for other columns, the id will be used.
renderHeader() => React.ReactNodeIf provided, this will be used to render the header component. When both columnName and renderHeader are provided, renderHeader will take precedence in the table header.
editable| true | ((object: Osdk.Instance<Q, "$allBaseProperties", PropertyKeys<Q>, RDPs>) => boolean)editable can be a boolean or a predicate that receives the row's object and returns whether the cell is editable
editFieldConfigEditFieldConfig<Osdk.Instance<Q, "$allBaseProperties", PropertyKeys<Q>, RDPs>>Configuration for the cell editor component.

When provided, the column uses the specified field component (e.g. dropdown) instead of the default auto-detected text/number input.

getFieldComponentProps receives the row's object and a map of any pending edits for that row (keyed by column id), and returns the props to pass to the field component. Editor configuration can depend on the current row or on other in-progress edits within the row.
validateEdit(value: unknown) => Promise<string | undefined>Additional function to validate the cell value during edit.

editable

editable accepts either a boolean or a function (rowData) => boolean:

  • editable: true — every cell in the column is editable.
  • editable: (rowData) => boolean — configurable per row. The function receives the row's data and returns whether the cell should be editable.
{
locator: { type: "property", id: "salary" },
// Only editable for active employees
editable: (employee) => employee.status === "Active",
}

When editable is a function, the column is still considered "potentially editable" at the table level — the bottom edit-mode bar is shown so users can enter and exit edit mode. The per-row predicate decides whether each cell renders the editor or the read-only value.

editFieldConfig

When editable is truthy, columns default to a text or number input (auto-detected from the property type). Use editFieldConfig to specify a different editor component.

Supported editor components:

fieldComponentDescriptionRenders
"DROPDOWN"A select dropdown or searchable comboboxSelect (default) or Combobox (when isSearchable: true)
"DATE_PICKER"A date or datetime pickerDatetimePicker

Without editFieldConfig, editable columns use a text input for string properties and a number input for numeric properties (double, integer, long, float, decimal, byte, short).

getFieldComponentProps receives the row's data and returns the props passed to the field component, so editor configuration can vary per row (e.g. dropdown items computed from the row's state).

{
locator: { type: "property", id: "department" },
editable: true,
editFieldConfig: {
fieldComponent: "DROPDOWN",
getFieldComponentProps: (employee) => ({
// Allow the user to pick from departments compatible with the
// employee's role
items: getCompatibleDepartments(employee.role),
}),
},
}

editFieldConfig is a discriminated union on fieldComponent. Each variant's getFieldComponentProps returns the config for that editor:

fieldComponent: "DROPDOWN"getFieldComponentProps returns:

Type parameters: V = unknown

NameTypeDescription
itemsV[]Required. Available items for the dropdown.
itemToStringLabel(item: V | undefined) => stringConverts an item to a display string. Defaults to String().

item may be undefined when the cell has no value yet — the formatter is responsible for producing a sensible label in that case.
itemToKey(item: V) => stringReturns a unique string key for a list item. Used as the React key. Falls back to the item's index when not provided.
isItemEqual(a: V, b: V) => booleanCustom equality check for item values. Defaults to Object.is. Required when items are objects to ensure correct selection matching.
isSearchablebooleanWhether the dropdown allows searching/filtering. When true, renders a Combobox with a search input. When false (default), renders a Select dropdown.
placeholderstringPlaceholder text shown when no value is selected.
isMultiplebooleanWhether multiple values can be selected.

fieldComponent: "DATE_PICKER"getFieldComponentProps returns:

NameTypeDescription
minDateThe earliest date the user can select.
maxDateThe latest date the user can select.
showTimebooleanWhether to show a time picker alongside the calendar.
closeOnSelectionbooleanWhether to close the popover after selecting a date. Defaults to true when showTime is false, false when showTime is true.
placeholderstringPlaceholder text shown when no value is selected.
formatDate(date: Date) => stringFormats a Date for display in the input field when not editing. Provide a matching parseDate if using a custom format.
parseDate(text: string) => Date | undefinedParses a user-typed string back into a Date. Must be the inverse of formatDate.

columnName vs renderHeader

  • columnName: If provided, this string is used as the column header text. If not provided, property columns default to the property's displayName, and other column types default to the id.
  • renderHeader: If provided, this function renders the header component. When both columnName and renderHeader are provided, renderHeader takes precedence in the table header, but columnName is still used in other places where the column name is displayed (e.g., the column configuration dialog, multi-sort dialog).

Column Locator Types

1. Property Column

Displays a property from the object type:

{
type: "property",
id: "propertyName" // Must be a valid property key
}

2. Derived Property (RDP) Column

Displays a computed property:

{
type: "rdp",
id: "customPropertyName",
creator: DerivedProperty.creator(/* ... */)
}

3. Function Column

Displays values computed by an OSDK function (query). This is equivalent to Workshop's function-backed columns. The function must accept an ObjectSet parameter and return a map of results keyed per object.

{
type: "function",
id: "columnKey", // Key in your FunctionColumns type map
queryDefinition: myQuery, // The OSDK query definition to execute
getFunctionParams: (objectSet) => ({ objectSetKey: objectSet }),
getKey: (object) => `${object.$objectType}:${object.$primaryKey}`, // The key to index the value of an object
getValue: (cellData) => cellData?.status, // Getter to extract the value from the raw data
dedupeIntervalMs: 5 * 60 * 1_000, // The stale time of your data, if multiple requests happen within this interval, no new network call will be made
}
PropertyTypeRequiredDescription
type"function"YesIdentifies this as a function column
idkeyof FunctionColumnsYesKey in the FunctionColumns type map
queryDefinitionQueryDefinitionYesThe OSDK query definition to execute
getFunctionParams(objectSet) => paramsYesComputes function parameters from the current ObjectSet
getKey(object) => stringYesGenerates a lookup key for each object in the result map
getValue(cellData?) => unknownNoExtracts a display value from the raw function result per object. cellData is undefined when the object has no result (e.g., loading or missing from the function output)
dedupeIntervalMsnumberNoMinimum time (ms) between re-fetches of the same function with the same parameters. Defaults to 300_000 (5 minutes)

4. Custom Column

Displays header and cell with the provided custom renderers.

{
type: "custom",
id: "columnName"
}

Examples

Example 1: Basic Table with Custom Column Definitions

import { Employee } from "@my/osdk";
import {
type ColumnDefinition,
ObjectTable,
} from "@osdk/react-components/experimental/object-table";

const columnDefinitions: Array<ColumnDefinition<typeof Employee>> = [
{
locator: { type: "property", id: "fullName" },
pinned: "left",
width: 200,
},
{
locator: { type: "property", id: "email" },
width: 250,
},
{
locator: { type: "property", id: "jobTitle" },
},
{
locator: { type: "property", id: "department" },
},
];

function EmployeesTable() {
return (
<ObjectTable
objectType={Employee}
columnDefinitions={columnDefinitions}
/>
);
}

Example 2: Table with Multiple Selection

import { Employee } from "@my/osdk";
import { ObjectTable } from "@osdk/react-components/experimental/object-table";

function EmployeesTable() {
return (
<ObjectTable
objectType={Employee}
selectionMode="multiple"
/>
);
}

Example 3: Table with Default Sorting

import { Employee } from "@my/osdk";
import { ObjectTable } from "@osdk/react-components/experimental/object-table";

function EmployeesTable() {
return (
<ObjectTable
objectType={Employee}
defaultOrderBy={[{
property: "firstFullTimeStartDate",
direction: "desc",
}]}
/>
);
}

Example 4: Custom Cell Rendering

import { Employee } from "@my/osdk";
import {
type ColumnDefinition,
ObjectTable,
} from "@osdk/react-components/experimental/object-table";

const columnDefinitions: Array<ColumnDefinition<typeof Employee>> = [
{
locator: { type: "property", id: "fullName" },
renderCell: (employee) => (
<strong style={{ color: "blue" }}>
{employee.fullName}
</strong>
),
},
{
locator: { type: "property", id: "firstFullTimeStartDate" },
renderCell: (employee) => {
const date = employee.firstFullTimeStartDate;
return date ? new Date(date).toLocaleDateString() : "-";
},
},
];

function EmployeesTable() {
return (
<ObjectTable
objectType={Employee}
columnDefinitions={columnDefinitions}
/>
);
}

Example 5: Custom Header Rendering

import { Employee } from "@my/osdk";
import {
type ColumnDefinition,
ObjectTable,
} from "@osdk/react-components/experimental/object-table";

const columnDefinitions: Array<ColumnDefinition<typeof Employee>> = [
{
locator: { type: "property", id: "fullName" },
renderHeader: () => (
<div style={{ display: "flex", alignItems: "center", gap: "8px" }}>
<span>👤</span>
<span>Employee Name</span>
</div>
),
},
];

function EmployeesTable() {
return (
<ObjectTable
objectType={Employee}
columnDefinitions={columnDefinitions}
/>
);
}

Example 6: Hidden Columns

Use isVisible: false to define columns that are hidden by default but can be toggled visible by the user:

const columnDefinitions: Array<ColumnDefinition<typeof Employee>> = [
{
locator: { type: "property", id: "fullName" },
},
{
locator: { type: "property", id: "email" },
},
{
locator: { type: "property", id: "jobTitle" },
isVisible: false, // Hidden by default
},
];

Example 7: Context Menu on Cell Right-Click

import { Employee } from "@my/osdk";
import { ObjectTable } from "@osdk/react-components/experimental/object-table";

function EmployeesTable() {
const renderCellContextMenu = (employee: Employee, cellValue: unknown) => (
<div
style={{
background: "white",
border: "1px solid #ccc",
borderRadius: "4px",
padding: "8px",
}}
>
<div onClick={() => console.log("View", employee.fullName)}>
View Details
</div>
<div onClick={() => console.log("Edit", employee.fullName)}>
Edit Employee
</div>
<div onClick={() => navigator.clipboard.writeText(String(cellValue))}>
Copy Value
</div>
</div>
);

return (
<ObjectTable
objectType={Employee}
renderCellContextMenu={renderCellContextMenu}
/>
);
}

Example 8: Row Click Handler

import { Employee } from "@my/osdk";
import { ObjectTable } from "@osdk/react-components/experimental/object-table";
import { useRouter } from "next/router";

function EmployeesTable() {
const router = useRouter();

const handleRowClick = (employee: Employee) => {
router.push(`/employees/${employee.$primaryKey}`);
};

return (
<ObjectTable
objectType={Employee}
onRowClick={handleRowClick}
/>
);
}

Example 9: Filtering on Object Properties and Derived Properties (RDPs)

You can filter by object properties and derived properties by including them in the WhereClause:

import { Employee } from "@my/osdk";
import { DerivedProperty } from "@osdk/client";
import {
type ColumnDefinition,
ObjectTable,
} from "@osdk/react-components/experimental/object-table";

type RDPs = {
managerName: string | undefined;
};

const columnDefinitions: Array<ColumnDefinition<typeof Employee, RDPs>> = [
{
locator: { type: "property", id: "fullName" },
},
{
locator: {
type: "rdp",
id: "managerName",
creator: DerivedProperty.creator<typeof Employee, string | undefined>(
(base) =>
base.lead.select({
fullName: true,
}),
(pivot) => pivot?.fullName,
),
},
renderHeader: () => <span>Manager</span>,
},
];

function EmployeesWithManagerTable() {
return (
<ObjectTable
objectType={Employee}
columnDefinitions={columnDefinitions}
filter={{
fullName: { $containsAnyTerm: "Paul" },
managerName: { $eq: "Jane Smith" },
}}
/>
);
}

Example 10: Controlled Sorting

import { Employee } from "@my/osdk";
import { ObjectTable } from "@osdk/react-components/experimental/object-table";
import { useState } from "react";

function EmployeesTable() {
const [orderBy, setOrderBy] = useState<
Array<{
property: keyof Employee;
direction: "asc" | "desc";
}>
>([
{ property: "fullName", direction: "asc" },
]);

return (
<ObjectTable
objectType={Employee}
orderBy={orderBy}
onOrderByChanged={setOrderBy}
/>
);
}

Example 11: Controlled Row Selection

import { Employee } from "@my/osdk";
import { ObjectTable } from "@osdk/react-components/experimental/object-table";
import { useState } from "react";

function EmployeesTable() {
const [selectedRows, setSelectedRows] = useState<string[]>([]);
const [isAllSelected, setIsAllSelected] = useState(false);

const handleRowSelectionChanged = ({ selectedRows, isSelectAll }) => {
setIsAllSelected(isSelectAll);
setSelectedRows(
isSelectAll ? [] : selectedRows.map((row) => row.$primaryKey),
);
};

return (
<div>
<div>Selected: {selectedRows.length} employees</div>
<ObjectTable
objectType={Employee}
selectionMode="multiple"
selectedRows={selectedRows}
isAllSelected={isAllSelected}
onRowSelectionChanged={handleRowSelectionChanged}
/>
</div>
);
}

Key points about select all behavior:

  • The isSelectAll field in the onRowSelectionChanged payload indicates whether the change was triggered by the "select all" checkbox
  • When isAllSelected is true, the table shows all rows as selected regardless of the selectedRows array content
  • This allows efficient handling of "select all" without loading all object IDs
  • Individual row selections automatically set isAllSelected to false
  • After "select all", new rows loaded via scroll (fetchMore) stay visually checked and onRowSelectionChanged refires with the expanded selection so controlled callers stay in sync

Listening to selection changes

onRowSelectionChanged is the preferred callback. It fires with a single payload covering everything you usually need:

<ObjectTable
objectType={Employee}
selectionMode="multiple"
onRowSelectionChanged={({
selectedRows,
isSelectAll,
objectSet,
}) => {
// selectedRows: loaded row instances currently selected.
// Pages not yet fetched are absent when isSelectAll.
// Use selectedRows.map(r => r.$primaryKey) if you
// need the primary keys.
// isSelectAll: true only when the user invoked "select all" (or
// controlled isAllSelected={true}) — NOT just because
// every visible row happens to be checked
// objectSet: ObjectSet covering the selection. Full underlying
// set when isSelectAll; otherwise narrowed by
// $primaryKey. `undefined` for interface types
// without a resolvable primaryKeyApiName on partial
// or empty selections.
if (objectSet) {
void applySomeBulkAction({ targets: objectSet });
}
}}
/>;

Example 12: Custom Column Type

In a custom column type, you can render anything in the column by passing in renderHeader and renderCell props.

import { Employee } from "@my/osdk";
import {
type ColumnDefinition,
ObjectTable,
} from "@osdk/react-components/experimental/object-table";

const columnDefinitions: Array<ColumnDefinition<typeof Employee>> = [
{
locator: {
type: "custom",
id: "Custom Column",
},
renderHeader: () => "Custom",
renderCell: (object: Osdk.Instance<Employee>) => {
return (
<button onClick={() => alert(`Clicked ${object["$title"]}`)}>
Click me
</button>
);
},
orderable: false,
},
];

function EmployeesTable() {
return (
<ObjectTable
objectType={Employee}
columnDefinitions={columnDefinitions}
/>
);
}

Example 13: Editable Table

Enable inline editing with validation, dropdown selectors, and bulk submission:

import { Employee, updateMultipleEmployees } from "@my/osdk";
import { useOsdkAction } from "@osdk/react";
import {
type CellEditInfo,
type ColumnDefinition,
ObjectTable,
} from "@osdk/react-components/experimental/object-table";

const columnDefinitions: Array<ColumnDefinition<typeof Employee>> = [
{
locator: { type: "property", id: "fullName" },
editable: true, // Default text input
},
{
locator: { type: "property", id: "email" },
editable: true,
validateEdit: async (value) => {
const emailRegex = /^[^\s@]+@[^\s@]+\.[^\s@]+$/;
return emailRegex.test(value as string)
? undefined
: "Please enter a valid email address";
},
},
{
locator: { type: "property", id: "department" },
editable: true,
editFieldConfig: {
fieldComponent: "DROPDOWN",
getFieldComponentProps: () => ({
items: [
"Engineering",
"Product",
"Design",
"Sales",
"Marketing",
"Finance",
"Human Resources",
],
}),
},
},
{
locator: { type: "property", id: "jobTitle" },
editable: true,
editFieldConfig: {
fieldComponent: "DROPDOWN",
getFieldComponentProps: () => ({
items: [
"Software Engineer",
"Senior Software Engineer",
"Staff Engineer",
"Engineering Manager",
"Product Manager",
"Designer",
],
isSearchable: true, // Renders a searchable combobox
placeholder: "Search job titles…",
}),
},
},
];

function EditableEmployeesTable() {
const { applyAction } = useOsdkAction(updateMultipleEmployees);

const handleCellValueChanged = (
info: CellEditInfo<Employee>,
) => {
console.log("Cell edited:", {
rowId: info.rowId,
columnId: info.columnId,
oldValue: info.oldValue,
newValue: info.newValue,
originalRowData: info.originalRowData,
});
};

// When onSubmitEdits is provided, a "Submit Edits" button appears in the table
const handleSubmitEdits = async (edits: CellEditInfo<Employee>[]) => {
try {
// Transform edits array into format expected by your action
const updates = edits.map(edit => ({
employeeId: edit.rowId,
field: edit.columnId,
value: edit.newValue,
}));

await applyAction({ updates });

// Return true to indicate successful submission
return true;
} catch (error) {
console.error("Failed to save edits:", error);
// Return false or throw to indicate failure
return false;
}
};

return (
<ObjectTable
objectType={Employee}
columnDefinitions={columnDefinitions}
editMode="manual" // User can toggle edit mode on/off
onCellValueChanged={handleCellValueChanged}
onSubmitEdits={handleSubmitEdits} // Shows "Submit Edits" button
/>
);
}

Key features of editable tables:

  1. Edit Modes:

    • manual (default): User clicks "Edit Table" button to enter edit mode
    • always: Table is always in edit mode
  2. Editor Components:

    • Text input (default): For string properties
    • Number input (auto-detected): For numeric properties (double, integer, long, float, decimal, byte, short)
    • Dropdown (Select): Fixed list of options via editFieldConfig with fieldComponent: "DROPDOWN"
    • Dropdown (Combobox): Searchable list via isSearchable: true in fieldComponentProps
  3. Validation:

    • Use validateEdit on columns for async validation
    • Validation errors are shown with an error icon and tooltip
    • Works with all editor types including dropdowns
  4. Edit State Management:

    • Edits are tracked locally until submitted
    • Modified cells are visually highlighted
    • "Cancel" button discards all pending edits
  5. Bulk Submission:

    • When onSubmitEdits is provided, a "Submit Edits" button appears
    • All edits are submitted together
    • Return true from onSubmitEdits to clear edits after successful submission

Per-Row Configuration for Editable and FieldComponentProps

Pass a function to editable to gate editing per row, and a getFieldComponentProps function to compute editor props from the row's data:

import { Employee } from "@my/osdk";
import {
type ColumnDefinition,
ObjectTable,
} from "@osdk/react-components/experimental/object-table";

const columnDefinitions: Array<ColumnDefinition<typeof Employee>> = [
{
locator: { type: "property", id: "salary" },
// Only editable for active employees
editable: (employee) => employee.status === "Active",
},
{
locator: { type: "property", id: "department" },
editable: true,
editFieldConfig: {
fieldComponent: "DROPDOWN",
// Items depend on the employee's role
getFieldComponentProps: (employee) => ({
items: getCompatibleDepartments(employee.role),
}),
},
},
];

Example 14: Custom Column Configuration Dialog

Use the ColumnConfigDialog component to create a custom column configuration experience:

import { Employee } from "@my/osdk";
import {
ColumnConfigDialog,
type ColumnDefinition,
ObjectTable,
} from "@osdk/react-components/experimental/object-table";
import { useCallback, useMemo, useState } from "react";

const initialColumnDefinitions: Array<ColumnDefinition<typeof Employee>> = [
{
locator: { type: "property", id: "fullName" },
columnName: "Full Name",
},
{
locator: { type: "property", id: "emailPrimaryWork" },
columnName: "Email",
},
{
locator: { type: "property", id: "jobTitle" },
columnName: "Job Title",
},
{
locator: { type: "property", id: "department" },
columnName: "Department",
},
{
locator: { type: "property", id: "businessTitle" },
columnName: "Business Title",
isVisible: false, // Hidden by default
},
];

function EmployeesTable() {
const [isColumnConfigOpen, setIsColumnConfigOpen] = useState(false);
const [columnDefinitions, setColumnDefinitions] = useState(
initialColumnDefinitions,
);

// Build column options for the dialog
const columnOptions = useMemo(
() =>
initialColumnDefinitions.map((colDef) => ({
id: colDef.locator.id,
name: colDef.columnName || colDef.locator.id,
})),
[],
);

// Track current visibility state
const currentVisibility = useMemo(() => {
const visibility: Record<string, boolean> = {};
initialColumnDefinitions.forEach((colDef) => {
visibility[colDef.locator.id] = columnDefinitions.some(
(def) => def.locator.id === colDef.locator.id,
);
});
return visibility;
}, [columnDefinitions]);

// Track current column order
const currentColumnOrder = useMemo(
() => columnDefinitions.map((colDef) => colDef.locator.id),
[columnDefinitions],
);

const handleApplyColumnConfig = useCallback(
(columns: Array<{ columnId: string; isVisible: boolean }>) => {
const newColumnDefinitions: Array<ColumnDefinition<typeof Employee>> = [];

// Apply the new visibility and order
columns.forEach(({ columnId, isVisible }) => {
if (isVisible) {
const colDef = initialColumnDefinitions.find(
(def) => def.locator.id === columnId,
);
if (colDef) {
newColumnDefinitions.push(colDef);
}
}
});

setColumnDefinitions(newColumnDefinitions);
setIsColumnConfigOpen(false);
},
[],
);

return (
<>
<div style={{ marginBottom: "16px" }}>
<button
onClick={() => setIsColumnConfigOpen(true)}
>
Configure Columns
</button>
</div>

<ObjectTable
objectType={Employee}
columnDefinitions={columnDefinitions}
enableColumnConfig={false} // Disable built-in config since we're using custom
/>

<ColumnConfigDialog
isOpen={isColumnConfigOpen}
onClose={() => setIsColumnConfigOpen(false)}
columnOptions={columnOptions}
currentVisibility={currentVisibility}
currentColumnOrder={currentColumnOrder}
onApply={handleApplyColumnConfig}
/>
</>
);
}

This example demonstrates:

  • Using the ColumnConfigDialog component for custom column management
  • Tracking column visibility and order in component state
  • Providing a custom button to open the dialog
  • Disabling the built-in column configuration to avoid conflicts
  • Managing hidden columns that can be toggled visible by users

Example 15: Function-Backed Columns

Display values computed by OSDK functions (queries) alongside regular property columns. Function columns automatically handle loading states, caching, and deduplication.

import { Employee, getEmployeeMetrics } from "@my/osdk";
import {
type ColumnDefinition,
ObjectTable,
} from "@osdk/react-components/experimental/object-table";

// Define a type map for your function columns
type EmployeeFunctionColumns = {
metrics: typeof getEmployeeMetrics;
};

const columnDefinitions: Array<
ColumnDefinition<
typeof Employee,
Record<string, never>,
EmployeeFunctionColumns
>
> = [
{
locator: { type: "property", id: "fullName" },
pinned: "left",
width: 200,
},
{
locator: { type: "property", id: "department" },
},
{
locator: {
type: "function",
id: "metrics",
queryDefinition: getEmployeeMetrics,
// Pass the current object set as a parameter to the function
getFunctionParams: (objectSet) => ({ employees: objectSet }),
// Generate a unique key for each object to look up its result
getKey: (employee) => `${employee.$objectType}:${employee.$primaryKey}`,
// Extract the specific value to display from the function result
getValue: (cellData) =>
(cellData as { score: number } | undefined)?.score,
// Cache results for 1 minute instead of the default 5
dedupeIntervalMs: 60_000,
},
columnName: "Performance Score",
},
];

function EmployeesWithMetricsTable() {
return (
<ObjectTable
objectType={Employee}
columnDefinitions={columnDefinitions}
/>
);
}

Multiple function columns sharing the same queryDefinition are automatically deduplicated into a single API call. Use different getValue functions to extract different fields from the same result:

const columnDefinitions: Array<
ColumnDefinition<
typeof Employee,
Record<string, never>,
EmployeeFunctionColumns
>
> = [
{
locator: {
type: "function",
id: "metrics",
queryDefinition: getEmployeeMetrics,
getFunctionParams: (objectSet) => ({ employees: objectSet }),
getKey: (emp) => `${emp.$objectType}:${emp.$primaryKey}`,
getValue: (cellData) => (cellData as { score: number })?.score,
},
columnName: "Score",
},
{
locator: {
type: "function",
id: "metrics",
queryDefinition: getEmployeeMetrics,
getFunctionParams: (objectSet) => ({ employees: objectSet }),
getKey: (emp) => `${emp.$objectType}:${emp.$primaryKey}`,
getValue: (cellData) => (cellData as { rank: string })?.rank,
},
columnName: "Rank",
},
];

Column Pinning

Pin columns to the left or right side of the table:

const columnDefinitions: Array<ColumnDefinition<typeof Employee>> = [
{
locator: { type: "property", id: "fullName" },
pinned: "left", // Stays visible when scrolling horizontally
},
{
locator: { type: "property", id: "email" },
pinned: "right",
},
];

Column Resizing

Control whether columns can be resized:

const columnDefinitions: Array<ColumnDefinition<typeof Employee>> = [
{
locator: { type: "property", id: "fullName" },
resizable: true,
minWidth: 150,
maxWidth: 500,
},
];

Listen to resize events:

<ObjectTable
objectType={Employee}
onColumnResize={(columnId, newWidth) => {
console.log(`Column ${columnId} resized to ${newWidth}px`);
}}
/>;

Disable Filtering or Sorting

Disable filtering or sorting globally:

<ObjectTable
objectType={Employee}
enableColumnPinning={false}
enableColumnResizing={false}
enableColumnConfig={false}
enableOrdering={false}
/>;

Or per column:

const columnDefinitions: Array<ColumnDefinition<typeof Employee>> = [
{
locator: { type: "property", id: "fullName" },
orderable: false,
},
];

Custom Row Height

Adjust row height for better readability:

<ObjectTable
objectType={Employee}
rowHeight={56} // Larger rows for more content
/>;

Row Attributes and Conditional Row Styling

Use getRowAttributes to apply custom HTML attributes (typically data-* attributes) to each <tr> element. This is the recommended pattern for conditional row styling — for example, changing a row's background color based on the underlying object's state.

import { Employee } from "@my/osdk";
import type { Osdk } from "@osdk/api";
import { ObjectTable } from "@osdk/react-components/experimental/object-table";
import { useCallback } from "react";

function EmployeesTable() {
const getRowAttributes = useCallback(
(employee: Osdk.Instance<typeof Employee>) => ({
"data-status": employee.status,
"data-overdue": employee.daysOverdue > 0 ? "true" : undefined,
}),
[]
);

return (
<ObjectTable
objectType={Employee}
className="employees-table"
getRowAttributes={getRowAttributes}
/>
);
}

Entries whose value is undefined are skipped, so you can include attributes conditionally without emitting empty values.

Then drive your row styling in CSS using attribute selectors. Row background colors come from --osdk-table-row-bg-default (and --osdk-table-row-bg-alternate for odd zebra rows) — overriding both on a <tr> for matching rows takes precedence:

.employees-table tr[data-status="Inactive"] {
--osdk-table-row-bg-default: #f3f4f6;
--osdk-table-row-bg-alternate: #f3f4f6;
color: #6b7280;
}

.employees-table tr[data-overdue="true"] {
--osdk-table-row-bg-default: #fef2f2;
--osdk-table-row-bg-alternate: #fef2f2;
}

.employees-table tr[data-status="Active"][data-overdue="true"] {
--osdk-table-row-bg-default: #fffbeb;
--osdk-table-row-bg-alternate: #fffbeb;
}

Notes:

  • Combine multiple attribute selectors to express priority (the most specific selector wins, per normal CSS rules).
  • The table sets its own attributes (data-selected, data-focused, data-row-parity, data-pinned) on rows and cells. Avoid using these names in getRowAttributes since they would override the built-in behavior.

Loading and Empty States

The ObjectTable automatically handles:

  • Loading state: Shows skeleton rows while data is loading
  • Empty state: Shows appropriate message when no data matches filters
  • Error state: Displays error messages if data fetching fails

No additional configuration needed - these states are built-in!

Infinite Scrolling

The ObjectTable automatically implements infinite scroll pagination, with page size of 50. As users scroll down, more data is loaded seamlessly. No configuration required!

Exporting Data

Pass a tableRef to obtain an ObjectTableHandle<Q, RDPs>. Its getSnapshot() method loads all matching rows and returns a format-agnostic snapshot of the table's columns, rows, and total match count, so you can export to CSV, Excel, JSON, the clipboard, or anywhere else. When the total row count exceeds rowLimit (default 10_000), the returned promise rejects (with a string error message); otherwise every matching row is loaded.

The snapshot reflects the table's current column visibility, ordering, and pinning. Property, derived-property, and function-backed columns are all included. Custom-rendered columns have no underlying value and are omitted. Each row exposes a getValue(columnId) accessor; cells are the raw value, or the thrown Error instance if a function-backed cell failed to load (the promise still resolves with the rest of the snapshot).

The snapshot also carries totalCount — the number of objects matching the underlying object set as reported by the API, encoded as a string (or undefined when no count was provided). It may exceed the number of loaded rows, so it's handy for surfacing "exported N of M".

import type { Employee } from "@my/osdk";
import {
ObjectTable,
type ObjectTableHandle,
} from "@osdk/react-components/experimental";
import { useRef } from "react";

type RDPs = Record<string, never>;

function EmployeeTableWithDownload() {
const tableRef = useRef<ObjectTableHandle<Employee, RDPs>>(null);

const downloadCsv = async () => {
const handle = tableRef.current;
if (handle == null) return;

const { columns, rows, totalCount } = await handle.getSnapshot();
console.log(`Exporting ${rows.length} of ${totalCount ?? "?"} rows`);

const escape = (value: unknown) => {
// Failed function-backed cells surface as the thrown Error instance —
// render a marker so a failure is distinguishable from an empty cell.
const text = value == null
? ""
: value instanceof Error
? "#ERROR"
: String(value);
return /[",\n]/.test(text) ? `"${text.replace(/"/g, "\"\"")}"` : text;
};
const csv = [
columns.map((column) => escape(column.name)).join(","),
...rows.map((row) =>
columns.map((column) => escape(row.getValue(column.id))).join(",")
),
].join("\n");

// Prepend a UTF-8 BOM so spreadsheet apps detect the encoding.
const blob = new Blob(["" + csv], { type: "text/csv;charset=utf-8" });
const url = URL.createObjectURL(blob);
const anchor = document.createElement("a");
anchor.href = url;
anchor.download = "employees.csv";
anchor.click();
URL.revokeObjectURL(url);
};

return (
<>
<button onClick={downloadCsv}>Download CSV</button>
<ObjectTable objectType={Employee} tableRef={tableRef} />
</>
);
}

getSnapshot() accepts an optional { rowLimit } that bounds the snapshot size — when the total row count exceeds it, the promise rejects with a string error message. row.getValue(columnId) returns the raw cell value (or the thrown Error instance for failed function-backed cells, or undefined for unknown column ids) — your formatter handles the rest.

Headless Hooks

ObjectTable is assembled from a set of building-block hooks that are exported so you can build a fully custom table while keeping OSDK data fetching, sorting, selection, editing, and snapshot behavior. Reach for these when you need markup or interactions that ObjectTable's props don't cover.

The hooks are unopinionated about rendering — they produce the state and column definitions you feed into your own @tanstack/react-table instance, which you construct in your app:

npm install @tanstack/react-table

⚠️ Match the @tanstack/react-table version. @osdk/react-components bundles its own copy of @tanstack/react-table, and the hook return types (ColumnDef, Table, SortingState, OnChangeFn, …) come from that copy. TanStack types are invariant in their type parameters, and this package augments @tanstack/react-table via declare module (adding table/column meta fields). If your app resolves a different @tanstack/react-table version than the one this package uses, you may hit confusing type errors — e.g. a ColumnDef or Table produced by these hooks reported as not assignable to the one from your copy, or the augmented meta fields missing.

Install a version that matches the one this package depends on (see @tanstack/react-table in @osdk/react-components's package.json) — and dedupe so a single copy is resolved (e.g. a pnpm overrides / npm overrides / yarn resolutions entry if a transitive dependency pulls in another version).

Available hooks (import from @osdk/react-components/experimental/object-table):

HookResponsibility
useObjectTableDataLoads rows (by type or from an object set), applies filter/sort/derived + function columns
useColumnDefsBuilds TanStack column definitions from columnDefinitions (or object metadata)
useTableSortingControlled/uncontrolled sort state ↔ OSDK orderBy
useRowSelectionSingle/multiple/range row selection (controlled or uncontrolled)
useSelectionColumnThe leading checkbox column definition
useColumnPinning / useColumnResize / useColumnVisibilityColumn pinning, sizing, and visibility/order state
useFocusedRowControlled/uncontrolled focused-row state
useEditableTableCell-edit session state (pending edits, validation, submit)
useFunctionColumnsDataFetches function-backed column values
useObjectTableSnapshotBuilds the getSnapshot() export handle for a table instance
useCellContextMenuPer-cell context-menu open/position state

A minimal custom table wiring data, columns, and sorting together:

import type { Employee } from "@my/osdk";
import {
useColumnDefs,
useObjectTableData,
useTableSorting,
} from "@osdk/react-components/experimental/object-table";
import {
flexRender,
getCoreRowModel,
useReactTable,
} from "@tanstack/react-table";

function CustomEmployeeTable() {
const { sorting, onSortingChange } = useTableSorting<Employee>({});
const { data, isLoading } = useObjectTableData<Employee>({
objectOrInterfaceType: Employee,
sorting,
});
const { columns } = useColumnDefs<Employee>(Employee);

const table = useReactTable({
data: data ?? [],
columns,
state: { sorting },
onSortingChange,
manualSorting: true,
getCoreRowModel: getCoreRowModel(),
getRowId: (row) => String(row.$primaryKey),
});

return (
<table aria-busy={isLoading}>
<thead>
{table.getHeaderGroups().map((group) => (
<tr key={group.id}>
{group.headers.map((header) => (
<th
key={header.id}
onClick={header.column.getToggleSortingHandler()}
>
{flexRender(
header.column.columnDef.header,
header.getContext()
)}
</th>
))}
</tr>
))}
</thead>
<tbody>
{table.getRowModel().rows.map((row) => (
<tr key={row.id}>
{row.getVisibleCells().map((cell) => (
<td key={cell.id}>
{flexRender(cell.column.columnDef.cell, cell.getContext())}
</td>
))}
</tr>
))}
</tbody>
</table>
);
}

Add useRowSelection + useSelectionColumn for selection, useColumnPinning / useColumnResize / useColumnVisibility for column state, and useObjectTableSnapshot for export — each returns state and change handlers you thread into useReactTable's state / on*Change options, exactly as ObjectTable does internally.

TypeScript Tips

Type-Safe Column Definitions

Use TypeScript generics to ensure type safety:

import { Employee } from "@my/osdk";
import {
type ColumnDefinition,
ObjectTable,
} from "@osdk/react-components/experimental/object-table";

type RDPs = {
managerName: string | undefined;
yearsOfService: number;
};

const columnDefinitions: Array<ColumnDefinition<typeof Employee, RDPs>> = [
// TypeScript will validate property names and types
{
locator: { type: "property", id: "fullName" }, // ✅ Valid
},
{
locator: { type: "property", id: "invalidProp" }, // ❌ Type error
},
];

Inferring Types from Object Type

Let TypeScript infer types from your OSDK object type:

import { Employee } from "@my/osdk";
import type { PropertyKeys } from "@osdk/client";

// PropertyKeys gives you all valid property names
type EmployeeProps = PropertyKeys<typeof Employee>;

Troubleshooting

Table not displaying data

  • Ensure your OSDK client is properly configured
  • Check that the object type is imported correctly
  • Verify network requests in browser DevTools

Type errors with columnDefinitions

  • Ensure you're using the correct type parameters: ColumnDefinition<typeof YourObjectType, RDPs, FunctionColumns>
  • Property IDs must exactly match property names from your object type

Selection not working

  • Ensure selectionMode is set to "single" or "multiple"
  • For controlled mode, provide both selectedRows and onRowSelectionChanged

Custom rendering not appearing

  • Ensure renderCell returns valid React elements
  • Check browser console for errors in your render function

Table has no styling or looks broken

  • Ensure you've imported @osdk/react-components/styles.css in your main CSS file
  • Check that the CSS import is in the correct location (application entry point)
  • Check browser DevTools to confirm CSS custom properties are loaded

Theming

The ObjectTable emits a stable set of data-* attributes on its rendered DOM, and exposes every visual property through --osdk-table-* CSS variables. Together they let you override appearance via the table's className (or any parent wrapper) without forking the component or relying on internal class names. See Prerequisites › Token scopes for the underlying --osdk-* / --bp-* token model.

The sub-sections below list the attributes and variables available on each rendered element, followed by override examples. CSS variables cascade, so you can override them on a parent element to affect every nested cell or row.

<thead> — Table header row container

Data attributes

AttributeValuesMeaning
data-resizingtrue | falseSet while the user is actively resizing a column.

CSS variables

VariableDefaultDescription
--osdk-table-header-height50pxHeader row height.
--osdk-table-header-bgvar(--osdk-background-secondary)Header background color.
--osdk-table-header-fontWeightvar(--osdk-typography-weight-bold)Header text weight.
--osdk-table-header-fontSizevar(--osdk-typography-size-body-small)Header text size.
--osdk-table-header-colorvar(--osdk-typography-color-muted)Header text color.
--osdk-table-header-dividervar(--osdk-table-border)Vertical divider between header cells.
--osdk-table-resizer-color-hovervar(--osdk-custom-color-primary-1)Resize handle hover color.
--osdk-table-resizer-color-activevar(--osdk-intent-primary-rest)Resize handle active color.

<th> — Header cell

Data attributes

AttributeValuesMeaning
data-pinnedleft | right | falseColumn pinning state.

CSS variables

VariableDefaultDescription
--osdk-table-pinned-column-bordervar(--osdk-table-border)Border for pinned columns.
--osdk-table-header-menu-paddingcalc(var(--osdk-surface-spacing) * 0.25)Menu button padding.
--osdk-table-header-menu-bgvar(--osdk-custom-color-light-gray-2)Menu button background.
--osdk-table-header-menu-bordervar(--osdk-surface-border-width) solid var(--osdk-custom-color-gray-4)Menu button border.
--osdk-table-header-menu-colorvar(--osdk-typography-color-muted)Menu icon color.
--osdk-table-header-menu-color-activevar(--osdk-typography-color-default-rest)Menu icon color when active.
--osdk-table-header-menu-icon-colorvar(--osdk-table-header-menu-color)Menu chevron color.
--osdk-table-header-menu-bg-hovervar(--osdk-custom-color-gray-1)Menu button hover background.
--osdk-table-header-menu-bg-activevar(--osdk-custom-color-gray-2)Menu button active background.

<tr> — Body row

Data attributes

AttributeValuesMeaning
data-selectedtrue | falseWhether the row is selected.
data-focusedtrue | falseWhether the row currently has focus (last-clicked row).
data-row-parityeven | oddRow index parity, for striping.

You can also attach custom data-* attributes per row with the getRowAttributes prop — see Row Attributes and Conditional Row Styling.

CSS variables

VariableDefaultDescription
--osdk-table-row-bg-defaultvar(--osdk-background-primary)Default row background.
--osdk-table-row-bg-alternatevar(--osdk-background-tertiary)Alternate (odd) row background.
--osdk-table-row-bg-hovercolor-mix(in srgb, var(--osdk-intent-primary-hover) 10%, var(--osdk-background-primary))Row hover background.
--osdk-table-row-bg-activecolor-mix(in srgb, var(--osdk-intent-primary-hover) 10%, var(--osdk-background-primary))Active/selected row background.
--osdk-table-row-border-color-hovervar(--osdk-intent-primary-rest)Border color for hovered rows.
--osdk-table-row-border-color-activevar(--osdk-intent-primary-rest)Border color for selected rows.
--osdk-table-row-dividervar(--osdk-table-border)Horizontal divider between rows.

<td> — Body cell

Data attributes

AttributeValuesMeaning
data-pinnedleft | right | falseMirrors the column's pinning state.
data-editabletrue | (absent)Present when the cell is editable in the current mode.

CSS variables

VariableDefaultDescription
--osdk-table-cell-padding0 calc(var(--osdk-surface-spacing) * 2)Cell padding.
--osdk-table-cell-fontSizevar(--osdk-typography-size-body-medium)Cell text size.
--osdk-table-cell-colorvar(--osdk-typography-color-default-rest)Cell text color.
--osdk-table-cell-bginheritCell background color.
--osdk-table-cell-dividervar(--osdk-table-border-width) solid transparentVertical divider between row cells.
--osdk-table-cell-editable-bordervar(--osdk-surface-border-width) solid var(--osdk-surface-border-color-strong)Border for editable cells in edit mode.
--osdk-table-cell-edited-bordervar(--osdk-surface-border-width) solid var(--osdk-intent-primary-rest)Border for edited cells with pending changes.
--osdk-table-cell-edited-border-errorvar(--osdk-surface-border-width) solid var(--osdk-intent-danger-rest)Border for cells with validation errors.
--osdk-table-cell-input-bgvar(--osdk-background-primary)Background for editable inputs.

Scope --osdk-table-cell-* overrides with td[data-editable] to target only editable cells.

Rendered when editMode is manual or when onSubmitEdits is provided.

VariableDefaultDescription
--osdk-table-edit-container-paddingcalc(var(--osdk-surface-spacing) * 2) calc(var(--osdk-surface-spacing) * 4)Padding for the edit controls container.
--osdk-table-edit-container-min-heightcalc(var(--osdk-surface-spacing) * 12)Minimum height for the edit controls container.

Column config dialog

Rendered when enableColumnConfig is true and the user opens the dialog.

VariableDefaultDescription
--osdk-table-column-config-dialog-min-width800pxMinimum width for the column config dialog.
--osdk-table-column-config-dialog-min-height400pxMinimum height for the column config dialog.
--osdk-table-column-config-visible-columns-bgvar(--osdk-background-secondary)Background for the visible columns section.

Skeleton loading rows

Shown while data is loading.

VariableDefaultDescription
--osdk-table-skeleton-color-fromvar(--osdk-background-skeleton-from)Skeleton animation start color.
--osdk-table-skeleton-color-tovar(--osdk-background-skeleton-to)Skeleton animation end color.

Shared border tokens

These feed into the per-element border variables above.

VariableDefaultDescription
--osdk-table-border-colorvar(--osdk-surface-border-color-default)Base color for all table borders.
--osdk-table-border-widthvar(--osdk-surface-border-width)Base width for all table borders.
--osdk-table-bordervar(--osdk-table-border-width) solid var(--osdk-table-border-color)Base table border (outermost edges).

See CSSVariables.md for the canonical reference of every --osdk-table-* token.

Override examples

Each example below scopes overrides under a className passed to <ObjectTable className="my-table" /> so other tables on the page are unaffected. Drop the class selector to apply globally via :root in the user.theme layer.

Editable cell background

Use the data-editable attribute that the table sets on every editable <td> to highlight only the cells the user can actually change. Pair it with --osdk-table-cell-editable-border to outline the cell in edit mode and --osdk-table-cell-edited-border to mark cells with pending changes.

<ObjectTable
objectType={Employee}
columnDefinitions={editableColumns}
editMode="manual"
className="my-table"
/>
/* Editable cells get a soft yellow background to signal they're interactive. */
.my-table td[data-editable="true"] {
--osdk-table-cell-bg: #fffbeb;
}

Row attributes for conditional row styling

Attach custom data-* attributes per row with the getRowAttributes prop and drive row styling in CSS using attribute selectors. Row background comes from --osdk-table-row-bg-default and --osdk-table-row-bg-alternate — overriding both ensures the override wins regardless of zebra parity.

import { useCallback } from "react";

const getRowAttributes = useCallback(
(employee: Osdk.Instance<typeof Employee>) => ({
"data-status": employee.status,
"data-overdue": employee.daysOverdue > 0 ? "true" : undefined,
}),
[]
);

<ObjectTable
objectType={Employee}
className="my-table"
getRowAttributes={getRowAttributes}
/>;
.my-table tr[data-status="Inactive"] {
--osdk-table-row-bg-default: #f3f4f6;
--osdk-table-row-bg-alternate: #f3f4f6;
color: #6b7280;
}

.my-table tr[data-overdue="true"] {
--osdk-table-row-bg-default: #fef2f2;
--osdk-table-row-bg-alternate: #fef2f2;
}

/* Combine selectors to express priority — most specific wins. */
.my-table tr[data-status="Active"][data-overdue="true"] {
--osdk-table-row-bg-default: #fffbeb;
--osdk-table-row-bg-alternate: #fffbeb;
}

Notes:

  • Entries whose value is undefined are skipped, so attributes can be conditional without emitting empty values.
  • The table reserves data-selected, data-focused, data-row-parity, and data-pinned on rows and cells — don't return those names from getRowAttributes.

See Row Attributes and Conditional Row Styling for the full pattern walkthrough.

Scoped overrides for a specific table

<ObjectTable objectType={Employee} className="custom-employee-table" />
.custom-employee-table {
--osdk-table-header-bg: #1e40af;
--osdk-table-header-color: #ffffff;
--osdk-table-row-bg-hover: #dbeafe;
}

Compact density

<ObjectTable objectType={Employee} className="compact-table" rowHeight={32} />
.compact-table {
--osdk-table-header-height: 36px;
--osdk-table-cell-padding: 0 8px;
}

Additional Resources