Custom Entity for Dual-Write Failing on Record Creation: “Field 'Product' must be filled in”

Finance and Operations/AX Developer Forum
1

I’ve been working on building a custom entity in Dynamics 365 Finance & Operations to support PowerApps integration via Dual-write. The main objective is to expose a curated set of fields from InventTable and related tables, so records can be viewed, created, or updated from Dataverse (and vice versa).

Some of the key fields we want to expose include:

  • Item Number (from InventTable)
  • Product Name (from EcoResProductTranslation)
  • NameAlias, Item Group, Item Cost, price, etc.
  • Custom attributes like Manufacturer Name (from EcoResProductAttributeValueV3)
  • Procurement Category, Project Category, and Product Lifecycle State

I’ve already structured the joins and confirmed that the entity reads data correctly in Excel and the OData feed.

Problem:

When attempting to create a new record via DMF or Excel Add-In, I get the following error:

Results. Field 'Product' must be filled in.
Results. validateWrite failed on data source 'InventTable (InventTable)'

This makes sense — Product is a required link to EcoResProduct, and I believe it’s typically autogenerated in the standard product creation logic (i.e., ReleasedProductV2Entity). But I’m unclear on whether I need to generate this manually, or if I’m missing some setup/configuration in my entity.

My Questions:

  1. Does ‘Product’ need to be autogenerated in my custom entity? If so, how is that typically done in standard entities like ReleasedProductV2Entity, and can I replicate that?
  2. Would it make more sense to extend ReleasedProductV2Entity and add my extra fields there? Or maybe Duplicate it since I don’t want to disturb any of the pre-existing entities.
  • I notice many of the fields I need already exist in this entity, and I’d prefer not to reimplement everything.
  • However, I want to make sure I’m not breaking or overwriting any standard behavior.
  1. If I continue with a standalone custom entity, is there a clean, supported way to generate the Product RecId on record creation? Anywhere I should be looking?
2

I would think you’d need to create the released product first and then update any fields on inventtable. ReleasedProductV2Entity should work. If you need to extend it, make a copy of that entity first and then modify the copy. That way, if MS decides to release another version, it won’t be deprecated.