Dynamics Community Forum Thread Details

NMFC Code Not Copied from Item Template During Engineering Change Order Process

Hello Experts,

We are on 10.0.48 version.

We are using the Engineering Change Management / Engineering Change Order (ECO) process in Dynamics 365 Finance & Operations.

When a new item is created through the ECO process, we have configured an Item Template and associated it with the appropriate Engineering Product Category / Product Release Policy.

The Item Template contains an NMFC code, and other key fields from the template are successfully copied to the newly created item. However, the NMFC code is not copied.

For example:

Item Template: NMFC code is populated.
Engineering Product Category: configured with the appropriate Product Release Policy.
ECO: creates the new engineering product successfully.
Other template fields: copied as expected.
NMFC code: remains blank.

What is confusing is that Microsoft's documentation for the Engineering Change Management Product Release Policy states that "All fields within the Warehouse FastTab are copied."

Since the NMFC code is located within the Warehouse FastTab, we expected the NMFC code to be copied from the Item Template when the item is created/released through the ECO process. However, this does not happen.

Questions:

Is the NMFC code intentionally excluded from the fields copied from an Item Template through the Engineering Product Release Policy?
If the Microsoft documentation states that all fields within the Warehouse FastTab are copied, why is the NMFC code not being copied?
Is there any standard configuration that allows the NMFC code to be copied automatically?
If this is not supported through configuration, what is the Microsoft-recommended approach to populate the NMFC code during the ECO/product-release process?
Is there any Microsoft documentation, known issue, or KB article explaining this behavior?

We are trying to determine whether this is standard product behavior, a documentation gap, or a potential product defect, and we would prefer to avoid customization if a standard solution is available.

Any guidance from Microsoft or the community would be greatly appreciated.

Categories:

Engaging with FastTrack

You should first verify the exact table and field behind the NMFC code, because the release policy’s “Warehouse FastTab” wording does not always mean every visible field is copied by the template framework. Some fields on the same FastTab can have separate copy logic or be skipped during engineering product release.

If the field is populated in the source template but consistently blank on the released item while other fields copy correctly, this looks worth reproducing in a clean environment and raising with Microsoft. The documentation wording suggests the expected behaviour should include it unless NMFC is specifically excluded.

You should also test the same template through a normal released product creation process. If NMFC copies there but fails only through ECO that would point to a gap or defect in the engineering release process rather than a template configuration issue.

Quick Links

Leaderboard > FastTrack for Dynamics 365