Skip to content
D365 Reference

EcoResProduct

mainShared across companies

The shared product master — one row per product across all companies; released products in InventTable point back to it by RecId

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

9 fields · 1 key

9 fields.

Table fields: key flag, field name, extended data type, description, data type, length, and quirk flags. 9 fields.
KeyFieldEDTDescriptionTypeLengthFlags
KeyDisplayProductNumberProductNumberThe product number shown to users; the natural key of the shared productstring20
ProductTypeWhether the product is an item or a serviceenum
SearchNameSearchable short name for the productstring60
RecIdRecIdThe 64-bit surrogate key released products reference by Productint64
InstanceRelationTypeSubtype discriminator of the shared product supertype — tells you whether the row is a distinct product or a product master with variantsint64
ServiceTypeFor service products, whether the service is a plain service or a rights/subscription typeenum
PdsCWProductWhether the product is catch-weight — quantities then carry both a nominal and an actual weight unitenum
EngChgProductOwnerIdEngineering product owner responsible for change management on the productstring
EngChgProductTypeRecId reference to the engineering product type controlling versioning rules for the productint64

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading EcoResProduct 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  : EcoResProduct The shared product master — one row per product across all companies; released products in InventTable point back to it by RecId
-- Purpose: Column-selected read of EcoResProduct — auto-generated from field metadata
-- Grain  : One row per DisplayProductNumber
-- 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
  p.displayproductnumber AS "The product number shown to users; the natural key of the shared product",
  p.producttype AS "Whether the product is an item or a service",  -- enum: decode p.producttype via GlobalOptionsetMetadata join — see quirks guide #enums
  p.searchname AS "Searchable short name for the product",
  p.recid AS "The 64-bit surrogate key released products reference by Product",
  p.instancerelationtype AS "Subtype discriminator of the shared product supertype — tells you whether the row is a distinct product or a product master with variants",
  p.servicetype AS "For service products, whether the service is a plain service or a rights/subscription type",  -- enum: decode p.servicetype via GlobalOptionsetMetadata join — see quirks guide #enums
  p.pdscwproduct AS "Whether the product is catch-weight — quantities then carry both a nominal and an actual weight unit",  -- enum: decode p.pdscwproduct via GlobalOptionsetMetadata join — see quirks guide #enums
  p.engchgproductownerid AS "Engineering product owner responsible for change management on the product",
  p.engchgproducttype AS "RecId reference to the engineering product type controlling versioning rules for the product"
FROM <catalog>.<schema>.ecoresproduct p
ORDER BY p.displayproductnumber;

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

  • InventTableEcoResProductRecId ref · N:1
    ON inventtable.product = ecoresproduct.recid
  • EcoResProductTranslationEcoResProductRecId ref · N:1
    ON ecoresproducttranslation.product = ecoresproduct.recid
  • UnitOfMeasureConversionEcoResProductRecId ref · N:1
    ON unitofmeasureconversion.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.