@@ -0,0 +1,51 @@
+---
+'@object-ui/app-shell': minor
+---
+
+The metadata-admin dataset preview resolves its dimension values to labels, like every other analytics chart on the platform.
+
+`@object-ui/core` exports one dimension-label net (`loadDimensionFieldMeta` →
+`resolveDimensionFieldMeta` → `deriveDimensionLabelMaps` / `localizeFieldOptions`
+→ `relabelDimensions`, objectui#4030 / PR #4324, widened by objectui#4330 /
+PR #4388), with the React half — the authenticated read and its locale-free memo
+— stated once in `@object-ui/react`'s `useDatasetDimensionLabels` (objectui#4389).
+Enumerating the analytics chart producers by their every non-test call site of
+`buildChartSeries` gives exactly three, and all three relabel immediately before
+charting: `plugin-dashboard`'s `DatasetWidget`, `plugin-report`'s
+`DatasetReportRenderer`, and `plugin-charts`' `ObjectChart`.
+
+`DatasetPreview` is a fourth analytics chart on a different construction, and it
+fell outside that enumeration because it never calls `buildChartSeries` — it
+handed `state.rows` to `ChartRenderer` exactly as they arrived. Nothing was
+missing structurally: the draft carries the base object and each dimension's
+field path, and the preview already resolved its measure captions through
+`headerLabel`. The call simply was not made, and nothing in the file declared
+the omission deliberate.
+
+Two user-visible readings change, and they are two different defects:
+
+- a **dotted** dimension (`crm_account.industry`) plotted the **raw stored
+  value**. The server resolves nothing for a dotted path — the options live on
+  the relationship's target — so without the client net there was nothing on the
+  axis but the enum (`MFG`). This is objectui#4053 / #4263's shape, one surface
+  over;
+- a **local** select plotted the object's **authored English** label on every
+  locale, objectui#4330's shape.
+
+Neither threw and neither was red: the axis rendered a plausible string where a
+label belonged. That matters most on this particular surface, because it is the
+screen an author uses to decide whether their dataset is right — a raw enum here
+reads as "my dataset is wrong" and invites editing a configuration that was
+correct.
+
+The rows are relabelled ONCE and fed to both the chart and the result table
+below it, which is what `DatasetWidget` and `DatasetReportRenderer` do for the
+same reason: relabelling only the axis would put `Manufacturing` on a bar and
+`MFG` in the row directly beneath it.
+
+Behaviour is unchanged wherever the net resolves nothing. The read is
+best-effort by construction — an unreachable relationship, a field with no
+`options`, or a failed metadata read leaves the rows exactly as the server sent
+them — and `relabelDimensions` is idempotent and never touches measure columns,
+so a server-resolved value passes straight through. No new vocabulary, config
+key or public surface: this is the existing net's fourth call site.
@@ -28,7 +28,7 @@
  */
 
 import * as React from 'react';
-import { describe, it, expect, vi, afterEach } from 'vitest';
+import { describe, it, expect, vi, beforeEach, afterEach } from 'vitest';
 import { render, screen, cleanup } from '@testing-library/react';
 // Same pre-warm as the sibling `DatasetPreview.test.tsx`, for the same reason:
 // the preview renders its chart behind `React.lazy(() => import(...))`, and
@@ -46,9 +46,31 @@ vi.mock('../../../providers/AdapterProvider', () => ({
   useAdapter: () => ({ queryDataset }),
 }));
 
+/**
+ * objectui#8187 — the preview now resolves its dimensions' option labels
+ * through the shared label net, which issues `GET /api/v1/meta/object/<name>`.
+ * happy-dom resolves that relative URL against `localhost:3000`, so without a
+ * double every test here reaches a real socket and the network-escape guard
+ * (objectui#6640) fails the file.
+ *
+ * The double serves the base object with NO select options, which is what these
+ * cases have always assumed: nothing resolves, `relabelDimensions` returns the
+ * server's rows by identity, and every assertion below is byte-identical to
+ * what it pinned before that card. Label resolution itself is pinned in
+ * `__tests__/DatasetPreview.dimensionLabels-8187.test.tsx`, not here.
+ */
+const realFetch = global.fetch;
+beforeEach(() => {
+  global.fetch = vi.fn(async () => ({
+    ok: true,
+    json: async () => ({ item: { name: 'opportunity', fields: {} } }),
+  })) as any;
+});
+
 afterEach(() => {
   cleanup();
   queryDataset.mockReset();
+  global.fetch = realFetch;
 });
 
 /**
 
@@ -1,6 +1,6 @@
 // Copyright (c) 2026 ObjectStack. Licensed under the Apache-2.0 license.
 
-import { describe, it, expect, vi, afterEach } from 'vitest';
+import { describe, it, expect, vi, beforeEach, afterEach } from 'vitest';
 import { render, screen, cleanup, waitFor } from '@testing-library/react';
 // DatasetPreview renders its chart behind
 // `React.lazy(() => import('@object-ui/plugin-charts'))`, and the "use the right
@@ -25,9 +25,31 @@ vi.mock('../../../providers/AdapterProvider', () => ({
   useAdapter: () => ({ queryDataset }),
 }));
 
+/**
+ * objectui#8187 — the preview now resolves its dimensions' option labels
+ * through the shared label net, which issues `GET /api/v1/meta/object/<name>`.
+ * happy-dom resolves that relative URL against `localhost:3000`, so without a
+ * double every test here reaches a real socket and the network-escape guard
+ * (objectui#6640) fails the file.
+ *
+ * The double serves the base object with NO select options, which is what these
+ * cases have always assumed: nothing resolves, `relabelDimensions` returns the
+ * server's rows by identity, and every assertion below is byte-identical to
+ * what it pinned before that card. Label resolution itself is pinned in
+ * `__tests__/DatasetPreview.dimensionLabels-8187.test.tsx`, not here.
+ */
+const realFetch = global.fetch;
+beforeEach(() => {
+  global.fetch = vi.fn(async () => ({
+    ok: true,
+    json: async () => ({ item: { name: 'opportunity', fields: {} } }),
+  })) as any;
+});
+
 afterEach(() => {
   cleanup();
   queryDataset.mockReset();
+  global.fetch = realFetch;
 });
 
 const baseProps = { type: 'dataset', name: 'sales', locale: 'en-US' as const };
 
@@ -25,8 +25,10 @@ import {
   formatMeasure,
   formatDimensionValue,
   buildDatasetFieldHelpers,
+  relabelDimensions,
   type DatasetResultField,
 } from '@object-ui/core';
+import { useDatasetDimensionLabels } from '@object-ui/react';
 import { builtinAggregateLabels, useSafeFieldLabel, useSafeTranslate, useDisplayLocale } from '@object-ui/i18n';
 
 // Lazy-loaded so the (recharts-backed) chart bundle only loads when a dataset
@@ -71,6 +73,43 @@ export function DatasetPreview({ draft }: MetadataPreviewProps) {
     return d.map((x) => String(x?.name ?? '')).filter(Boolean);
   }, [draft]);
 
+  /**
+   * The dataset's `dimension name -> field path` map, read off the DRAFT.
+   *
+   * This is the same map the analytics result reports as `dimensionFields` and
+   * that the three other producers feed the net from — but the draft is the
+   * authority HERE, because this surface previews a possibly-unsaved dataset:
+   * the draft's `dimensions[].field` is present before any server round-trip,
+   * and no result echo is needed to know it. A dotted path (`crm_account
+   * .industry`) resolves against the relationship TARGET, which is the whole
+   * reason the path — not the dimension name — is what the net walks.
+   */
+  const dimensionFields = React.useMemo(() => {
+    const d = Array.isArray((draft as any).dimensions) ? ((draft as any).dimensions as Array<Record<string, unknown>>) : [];
+    const out: Record<string, string> = {};
+    for (const x of d) {
+      const name = String(x?.name ?? '');
+      const field = String(x?.field ?? '');
+      if (name && field) out[name] = field;
+    }
+    return out;
+  }, [draft]);
+
+  // objectui#8187 — the dimension-label net (objectui#4030 / PR #4324, widened
+  // by objectui#4330 / PR #4388), at its FOURTH call site. Analytics groups by
+  // a select's STORED value and resolves nothing at all for a dotted path, so
+  // without this the axis below plots `MFG` where `Manufacturing` belongs — and
+  // a local select plots the object's authored English on every locale. This is
+  // the screen an author uses to judge "is my dataset right?", so a raw enum
+  // here reads as "my dataset is wrong" and invites editing a correct one.
+  //
+  // The hook is the shared React half of that one net (`@object-ui/react`, the
+  // glue objectui#4389 stated once) — it holds the authenticated read and keeps
+  // the fetched metadata LOCALE-FREE, so switching language re-labels in place
+  // instead of re-fetching. Called above the early returns below, as the rules
+  // of hooks require; it issues no read when there is no object or no dimension.
+  const dimensionLabels = useDatasetDimensionLabels(objectName, dimensionFields, dimensionNames);
+
   const canRun = !!objectName && measureNames.length > 0;
 
   const [state, setState] = React.useState<PreviewState>({ status: 'idle', rows: [] });
@@ -147,6 +186,18 @@ export function DatasetPreview({ draft }: MetadataPreviewProps) {
     builtinAggregateLabels(tt),
   );
   const columns = [...dimensionNames, ...measureNames];
+  /**
+   * The rows as they are DISPLAYED — dimension values resolved to their option
+   * labels. Derived once and fed to BOTH the chart and the table, exactly as
+   * `DatasetWidget` and `DatasetReportRenderer` do: relabelling only the axis
+   * would put `Manufacturing` on a bar and `MFG` in the row directly beneath it.
+   *
+   * Idempotent and best-effort by construction — a value with no mapping (the
+   * server already resolved it, a lookup id, free text) passes through, and a
+   * failed metadata read leaves `dimensionLabels` null and returns `state.rows`
+   * by identity. Measure columns are never touched.
+   */
+  const displayRows = relabelDimensions(state.rows, dimensionLabels);
 
   // A ratio/percent measure (format like `0.0%`) on the same axis as a
   // magnitude measure (currency in the hundred-thousands) renders as an
@@ -209,7 +260,7 @@ export function DatasetPreview({ draft }: MetadataPreviewProps) {
               <div className="rounded-md border p-2">
                 <ChartRenderer
                   schema={{
-                    data: state.rows as Array<Record<string, unknown>>,
+                    data: displayRows,
                     xAxisKey: dimensionNames[0],
                     chartType: mixedScale ? 'combo' : 'bar',
                     series: measureNames.map((m) => ({
@@ -240,7 +291,7 @@ export function DatasetPreview({ draft }: MetadataPreviewProps) {
                 </tr>
               </thead>
               <tbody>
-                {state.rows.map((row, i) => (
+                {displayRows.map((row, i) => (
                   <tr key={i} className="border-t">
                     {columns.map((c) => (
                       <td key={c} className="px-2 py-1 tabular-nums whitespace-nowrap">