D365 Reference
RouteTable
mainRoute header — one row per route identifier with its name and approval state; route versions assign it to items, and Route rows hold its operation sequence
Module: Production ControlCompany-partitioned (DataAreaId)
Header & line
RouteTable is the header for its lines in Route.
Fields
6 fields · 1 key
| Key | Field | EDT | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Key | RouteId | RouteId | The route identifier — the natural key operations and versions join on | string | 20 | |
| Name | Route name | string | 60 | |||
| ItemGroupId | Item group used to filter and organize routes | string | ||||
| Approved | Whether the route header is approved for use | enum | ||||
| Approver | RecId | RecId of the worker who approved the route | int64 | |||
| CheckRoute | Whether route network validation is enforced | enum |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading RouteTableon Databricks — enums are decoded, 1900-01-01 dates are wrapped to NULL, and the DataAreaId anchor is in place. Set your Unity Catalog location, company, and filter values below; they’re substituted into the SQL and the copy button.
Query parameters
-- ============================================================
-- Table : RouteTable Route header — one row per route identifier with its name and approval state; route versions assign it to items, and Route rows hold its operation sequence
-- Purpose: Column-selected read of RouteTable — auto-generated from field metadata
-- Grain : One row per company (dataareaid) + RouteId
-- Notes : Auto-generated skeleton for Synapse Link / Fabric Link-landed F&O data (lowercase column names). Enums decoded inline where verified; datetimes stored in UTC; 1900-01-01 dates are sentinels mapped to NULL. System/audit columns omitted — see the quirks guide.
-- ============================================================
SELECT
r.routeid AS "The route identifier — the natural key operations and versions join on",
r.name AS "Route name",
r.itemgroupid AS "Item group used to filter and organize routes",
r.approved AS "Whether the route header is approved for use", -- enum: decode r.approved via GlobalOptionsetMetadata join — see quirks guide #enums
r.approver AS "RecId of the worker who approved the route",
r.checkroute AS "Whether route network validation is enforced" -- enum: decode r.checkroute via GlobalOptionsetMetadata join — see quirks guide #enums
FROM <catalog>.<schema>.routetable r
WHERE
r.dataareaid = '<company>'
ORDER BY r.routeid;3 parameters not filled: <catalog>, <schema>, <company>
Relationships
1-hop neighbors — click a table to navigate there. RecId and InventDim edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
ON routetable.routeid = route.routeidON prodtable.routeid = routetable.routeidON routeversion.routeid = routetable.routeid
Data Entities That Expose This Table
Route export entities exist in Data management, but their programmatic names could not be primary-source verified — land the raw tables.