Find information on Release 10.0.46.21 (February 2026) of PLM Integration for Engineering Change Management for Microsoft D365 F&SCM.
What’s new
New or changed features in Release 10.0.46.21 (February 2026) - PLM Integration for Engineering Change Management.
1. State-Based Product Release Automation
Feature Overview
State-Based Product Release Automation enables the system to evaluate product lifecycle states during PLM staging journal posting and automatically release only those products that meet defined state conditions. This ensures that products are released to operational companies only when they reach the appropriate lifecycle state, such as Approved or Released.
Key Benefits
Lifecycle State Validation: Release automation triggers only when defined product lifecycle state conditions are satisfied during staging journal posting.
Selective Release: Only products matching all state conditions are selected for automatic release; non-matching items are skipped.
Flexible State Rules: Configure single or multiple state conditions using a comma delimiter (e.g., State = Approved, Released, Draft) to match any of the listed states.
Detailed Logging: The system logs which items were released and which were skipped due to state mismatch, ensuring full traceability.
2. Combined Attribute and State Product Release Automation
Feature Overview
Combined Attribute and State Automation extends the release automation engine to evaluate both attribute-based and state-based conditions simultaneously. Automatic release triggers only when all combined conditions are fulfilled, providing precise control over which products are released.
Key Benefits
Dual-Condition Evaluation: The system evaluates each imported item against both attribute and state-based rules before triggering a release.
Precise Targeting: Only items matching all combined conditions (e.g., Material = METAL AND State = Approved) are selected for automatic release.
Multi-Value Support: Configure multiple attribute and state values using a comma delimiter (e.g., Material = METAL, PLASTIC and State = Approved, Released) to match any of the listed values for each condition.
Comprehensive Logging: Log records capture which items were released and which were skipped due to rule mismatch.
3. Product Release on Specified Legal Entities per Engineering Product Category
Feature Overview
This feature enables users to define, for each Engineering Product Category, the specific legal entities in which products should be released when product release automation is active. The available legal entities for selection are limited to those defined in the product release policies associated with the engineering product category.
Key Benefits
Targeted Legal Entity Release: Select one or more legal entities per Engineering Product Category to control exactly where products are released.
Policy-Driven Selection: The list of selectable legal entities is always a subset of those defined in the product release policy, ensuring compliance.
Flexible Defaults: If no legal entity is selected, the system defaults to releasing products in all legal entities defined in the product release policy.
Combined with Filters: Legal entity selection works in combination with attribute and state filters for fine-grained control.
4. Licensing
This release includes TCL Common model version 1.0.0.63, which contains a new license certificate. After deploying this release, you must reinstall all STAEDEAN licenses as described in KB0018522.
Note
If you have already installed TCL Common model version 1.0.0.63 and reinstalled all STAEDEAN licenses, you can skip this step.
Bug fixes
Bug fixes in Release 10.0.46.21 (February 2026) - PLM Integration for Engineering Change Management.
Bug Number | Title | Description |
|---|---|---|
235118 | Staging journal version field truncated at 10 characters | The version field in the PLM staging journal was being truncated at 10 characters for distinct products, even though D365 supports up to 20 characters. This caused issues for customers with longer version numbering schemes. The field length has been corrected to support up to 20 characters for distinct products. Product master items retain the standard 10-character limit per D365 constraints. |
216818 | Product owner value not validated against system values | When importing products with a product owner ID not configured in the system, the staging journal did not block the import. This allowed assigning a non-existent product owner to a product. The system now validates the product owner value against the reference table during import and raises an error when the value does not exist. |
231141 | Product name and description not updating through PLM Integration | Product name and description were no longer updating on the released product when changes were sent through the PLM Integration. The updates were applied to product variants but not to the released product itself. This issue has been resolved, and both fields now update correctly on the released product. |
231418 | Configuration field in staging journal has incorrect length | The configuration (Config) field in the staging journal only accepted 10 characters, while D365 supports up to 50 characters. This blocked processes for customers using longer configuration identifiers. The field length has been corrected to 50 characters, matching the D365 standard. |
231507 | Migrated engineering documents not recognized by ECO using ImportECO | When engineering documents were migrated to an engineering version using the Engineering Document data entity with the PLM reference pre-populated, ImportECO failed to recognize these documents. The staging journal would lock or fail during processing. This issue has been resolved so that migrated documents with pre-populated PLM references are correctly recognized during ImportECO processing. |
231252 | AI endpoint error shown when AI summary is disabled | An error message related to STAEDEAN AI endpoint and key configuration was displayed when opening the BOM Comparison workspace, even when the AI Summary feature was disabled. The system now correctly suppresses AI-related error messages when the Enable AI Summary toggle is set to Off. |
231755 | Incorrect documents shown in downstream impact view | The Downstream Impact View Documents section in BOM Comparison displayed random or unrelated document information when no documents were associated with the ECO. This could lead to incorrect block and notify operations. The system now correctly shows an empty document list when no relevant documents are associated. |
233320 | Description not updated for new staging journal lines in BOM Comparison | When creating a new staging journal and adding BOM lines, the item descriptions were not displayed in the BOM Comparison workspace. This prevented users from viewing complete item information during change analysis. The system now correctly populates and displays item descriptions for all BOM lines in the BOM Comparison view. |
Known issues
Known issues in Release 10.0.46.21 (February 2026) - PLM Integration for Engineering Change Management.
Issue | Description |
|---|---|
Multi BOM Scenario Limitation | The multi BOM scenario in an ImportECO process is currently not supported when not all BOMs are transferred to a new version. The Engineering Change Management (ECM) module does not allow deleting an existing BOM that is not carried over to the new version. This limitation may require manual adjustments to ensure consistency in BOM versions. |
PLM Integration Migration | When migrating the PLM Integration project from one environment to another, the engineering attributes and attribute types attached to the PLM system are created in the new environment. However, if a fixed list on an attribute type contains pre-populated values, these values are not automatically migrated. Users must manually populate these lists in the new environment to maintain data integrity. |
Translation Gaps for New Fields | The labels for newly introduced fields have not yet been translated into several languages. This issue is expected to be resolved in an upcoming release. In the meantime, users may encounter untranslated labels in non-English environments, which could impact usability for multilingual teams. |
Appendix
The package consists of a deployable package containing the following models and their respective versions. These models are essential for the functionality and integration of the PLM and Business Integration solutions.
Solution | Model Name | Version |
|---|---|---|
PLM | Product Lifecycle Management Labels | 10.0.46.21 |
PLM | Product Lifecycle Management Licenses | 10.0.46.21 |
PLM | Product Lifecycle Management | 10.0.46.21 |
PLM | Product Lifecycle Management BIS | 10.0.46.21 |
PLM | Product Lifecycle Management Data Upgrade | 10.0.46.21 |
Connectivity Studio | Business Integration Labels | 10.0.46.71 |
Connectivity Studio | Business Integration Licenses | 10.0.46.71 |
Connectivity Studio | Business Integration | 10.0.46.71 |
Connectivity Studio | Business Integration Master Data Management | 10.0.46.71 |
Common | TCLCommon | 1.0.0.63 |
Common | TCLLabel | 1.0.0.63 |
Note
Ensure that all models are deployed and verified in the target environment to maintain compatibility and functionality across the PLM and Business Integration solutions.