D365 Reference
EcoResProductTranslation
mainShared across companiesLanguage-specific product names and descriptions — one row per shared product and language, joined back to EcoResProduct by RecId; the table product names actually live in
Module: Product InformationNo company partition
What the badges mean
- main
- Table group: how F&O categorizes the table's role — main entity, group/header, transaction, worksheet header, worksheet line, reference, parameter, or framework.
- Shared across companies
- The table carries no
DataAreaId— rows aren’t partitioned per company, so a query never needs (and can’t use) a company filter here (see the quirks guide). - Date-effective
- The table carries a
ValidFrom/ValidToeffectivity window — a join without a date filter multiplies every key by its history (see the quirks guide).
In field listings, K marks a key field.
Fields
4 fields · 2 key
4 fields.
| Key | Field | EDT | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Key | Product | RecId | RecId of the shared product in EcoResProduct this translation belongs to | int64 | ||
| Key | LanguageId | Language code of the translation; product + language is the natural key | string | |||
| Name | Product name in this language — the display name most reports actually want | string | ||||
| Description | Longer product description in this language | string |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading EcoResProductTranslation on 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
2 parameters not filled: <catalog>, <schema>
-- ============================================================
-- Table : EcoResProductTranslation Language-specific product names and descriptions — one row per shared product and language, joined back to EcoResProduct by RecId; the table product names actually live in
-- Purpose: Column-selected read of EcoResProductTranslation — auto-generated from field metadata
-- Grain : One row per Product + LanguageId
-- 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
e.product AS "RecId of the shared product in EcoResProduct this translation belongs to",
e.languageid AS "Language code of the translation; product + language is the natural key",
e.name AS "Product name in this language — the display name most reports actually want",
e.description AS "Longer product description in this language"
FROM <catalog>.<schema>.ecoresproducttranslation e
-- Resolve EcoResProduct (via Product): uncomment to join on its RecId surrogate key
-- LEFT JOIN <catalog>.<schema>.ecoresproduct eco ON eco.recid = e.product
ORDER BY e.product;Verified September 2026
Relationships
Diagram of 1-hop neighbors — join details below. RecId and InventDim edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
ON ecoresproducttranslation.product = ecoresproduct.recid
Data Entities That Expose This Table
- EcoResProductTranslationEntity — Product translations — one record per product and language with the localized name and description, keyed by product numberPrimary source
- EcoResProductV2Entity — Products — the shared product master export (displayed as 'Products V2'), carrying product type, dimension-group assignments, and translated name and description
More Product Information tables
- EcoResStorageDimensionGroupStorage dimension group master — shared setup that decides which storage dimensions (site, warehouse, location) are active and mandatory for the products assigned to it, including whether advanced warehousing applies
- EcoResTrackingDimensionGroupTracking dimension group master — shared setup that decides whether batch and serial tracking are active for the products assigned to it, and where serials are captured
- InventItemGroupItem group master — one row per company and item group, the reporting and posting bucket items are assigned to via InventItemGroupItem
- InventItemGroupItemThe link table that assigns each released item to its item group — in D365 the item group is NOT a column on InventTable; this table is where the assignment lives. Cross-company: it carries explicit ItemDataAreaId / ItemGroupDataAreaId columns instead of a DataAreaId partition
- InventModelGroupItem model group master — one row per company and model group, controlling inventory policy for its items: costing model, negative-stock rules, and whether the product is stocked at all
- InventModelGroupItemThe link table that assigns each released item to its item model group — like the item group, the model group is not a column on InventTable. Cross-company, with explicit ItemDataAreaId / ModelGroupDataAreaId columns