Find information on Release 10.0.48.23 (July 2026) of PLM Integration for Engineering Change Management for Microsoft D365 F&SCM.
Version information:
Product | Version | Minimum version | Latest validated version | Planned next |
|---|---|---|---|---|
PLM Integration for Engineering Change Management | 10.0.48.23 | D365 F&SCM 10.0.45 | D365 F&SCM 10.0.48 | On demand |
What’s new
New or changed features in Release 10.0.48.23 (July 2026) of PLM Integration for Engineering Change Management.
1. Transfer failed lines when posting a PLM staging journal
You can now post a PLM staging journal even when some lines fail validation. Valid lines post immediately. The system moves the lines that fail validation to a new PLM staging journal, called the error journal, so you can correct them and post them again.
A new Transfer failed lines toggle controls this behavior. It works like the standard Transfer errors toggle on the Post journals page in Dynamics 365. The toggle defaults to off, so current posting behavior stays the same until you turn it on.
Key capabilities:
The Transfer failed lines toggle appears on the manual Post journal page and on all three batch posting menus: Post staging journals, Post migration staging journals, and Post release staging journals.
When all lines pass validation, the system posts all lines and creates no error journal.
When some lines fail, the system posts the valid lines and moves the failing lines to a new error journal.
When all lines fail, the system posts no lines and moves all lines to a new error journal.
Related lines stay together. If one line in a group fails, the system moves the whole group, including its header, child lines, and linked documents, to the error journal.
The error journal shows the Original journal number, so you can trace it back to the source journal.
You can navigate between the source journal and its error journals from the journal.
When you post an error journal again with the toggle on, any remaining failures create a further error journal.
See also: Transfer errors to a new staging journal
2. Configurable multi-language translation updates
PLM multi-language translations apply when a product is created for the first time. Before this release, a re-import of the same product with translation changes updated only the product variants. The main product translation stayed unchanged.
You can now control this behavior with a new Translation update strategy field on the PLM systems page. You choose whether translation updates from PLM re-imports apply to the product variants only or to both the main product and its variants. Existing products can also receive new translations and updates to existing translations.
Key capabilities:
A new Translation update strategy field on the PLM systems page controls how translation updates apply.
Select Variant-only updates to apply translation updates to the product variants only. This keeps the current behavior.
Select Product and variant updates to apply translation updates to both the main product and its variants.
Existing products receive new translations and updates to existing translations on re-import.
Bugs
Resolved issues in Release 10.0.48.23 (July 2026) of PLM Integration for Engineering Change Management.
Bug number | Title | Description |
|---|---|---|
243662 | Route Versions must accept the Routes based on date range | You can now add several routes with the same route number and different date ranges to a staging journal. The staging journal matches the standard routes form and no longer shows a record already exists message. |
245996 | Staging journal posting does not recognize approver from PLM system for Link Route / route version | The staging journal now recognizes the approver from the PLM system when you post a link route or route version. Posting no longer fails for an approver that already works for BOMs and standard import routes. |
245997 | Staging journal does not recognize that release automation is disabled when setup is in place | The staging journal now respects a disabled release automation setup. The system no longer requires a receiving company on the link route message or a release automation record when release automation is off. |
246947 (CS00240596) | Wrong product search name | The product search name now comes from the value in the XML import. The product search name matches the item search name and is no longer overwritten with an unexpected value. |