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. |