docs(table-pivot): verbatim column naming and the sanitize option

[rad-pat]

Documents the Table Pivot column-naming change from PlaidCloud/plaid#6493.

• Table Pivot reference (table-pivot.mdx): a new New Column Naming section — a pivot names its new columns after the source category values exactly as they appear by default; the new Sanitize new column names option replaces spaces and punctuation with underscores (e.g. Freight Revenue → Freight_Revenue), and Alteryx CrossTab imports enable it automatically.
• What's New — July 2026: a Fixed entry noting pivot column names keep their spaces again, plus the new sanitize option.

Related product PRs (deploy together): PlaidCloud/plaid#6493, PlaidCloud/workflow-runner#1089, PlaidCloud/PlaidClient#1785.

🤖 Generated with Claude Code

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	plaidcloud-docs	f984965	Commit Preview URL Branch Preview URL	Jul 08 2026, 08:23 AM

[simozzy]

Review — Table Pivot verbatim column naming + sanitize option

Small, clean docs PR (7 lines) documenting the pivot column-naming change from PlaidCloud/plaid#6493. I cross-checked every claim against the product PRs and it's accurate:

• Verbatim default — matches the backend (query.pivot(..., sanitize_column_names=False); REST model Field(False, …, "default keeps the raw category value")).
• Option label — the client checkbox (PlaidClient#1785) is "Sanitize new column names (spaces and punctuation become underscores)"; the doc's bolded Sanitize new column names matches its leading text, and the parenthetical behaviour the doc describes matches the label's own.
• Freight Revenue → Freight_Revenue — identical to the example in PlaidClient#1785.
• Alteryx CrossTab auto-enable — confirmed in the backend test (the Alteryx-converter path) and the client PR.
• MDX is safe — examples are in backticks, so no {…} JSX-expression gotcha; the /reference/workflow-steps/tables/table-pivot/ link resolves to the existing page.

No new step is added (section appended to an existing page), so no category-index or LinkCard update is owed. The July release note is correctly placed as a Fixed entry and the "keep their spaces again" framing matches the regression being fixed.

No blocking findings. One cosmetic nit only: the insertion leaves two consecutive blank lines before ## Table Data Selection (the added + blank line plus the pre-existing one) — Markdown collapses it, drop one if you're touching the file again. Not worth a re-push on its own.

LGTM.