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
Fields
4 fields · 2 key
| 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 EcoResProductTranslationon 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 : 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;2 parameters not filled: <catalog>, <schema>
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 ecoresproducttranslation.product = ecoresproduct.recid
Data Entities That Expose This Table
- EcoResProductTranslationEntityProduct translations — one record per product and language with the localized name and description, keyed by product numberPrimary source
- EcoResProductV2EntityProducts — the shared product master export (displayed as 'Products V2'), carrying product type, dimension-group assignments, and translated name and description