Skip to content
D365 Reference

EcoResProductTranslation

mainShared across companies

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

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/ValidTo effectivity 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.

Table fields: key flag, field name, extended data type, description, data type, length, and quirk flags. 4 fields.
KeyFieldEDTDescriptionTypeLengthFlags
KeyProductRecIdRecId of the shared product in EcoResProduct this translation belongs toint64
KeyLanguageIdLanguage code of the translation; product + language is the natural keystring
NameProduct name in this language — the display name most reports actually wantstring
DescriptionLonger product description in this languagestring

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

  • EcoResProductTranslationEcoResProductRecId ref · N:1
    ON ecoresproducttranslation.product = ecoresproduct.recid

Data Entities That Expose This Table

More Product Information tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Microsoft. Microsoft, Dynamics 365, and Microsoft Fabric are trademarks of the Microsoft group of companies.