web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
FastTrack for Dynamics 365 forum
Unanswered

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

(0) ShareShare
ReportReport
Posted on by

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:

  1. Is the NMFC code intentionally excluded from the fields copied from an Item Template through the Engineering Product Release Policy?
  2. If the Microsoft documentation states that all fields within the Warehouse FastTab are copied, why is the NMFC code not being copied?
  3. Is there any standard configuration that allows the NMFC code to be copied automatically?
  4. If this is not supported through configuration, what is the Microsoft-recommended approach to populate the NMFC code during the ECO/product-release process?
  5. 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.

I have the same question (0)

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the July Top 10 Community Leaders

These are the community rock stars!

Leaderboard > FastTrack for Dynamics 365

#1
Muhammad Shahzad Shafique Profile Picture

Muhammad Shahzad Sh... 14 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 6 Super User 2026 Season 2

#3
Hamza H Profile Picture

Hamza H 4 Super User 2026 Season 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans