cm.abstract.part

AbsPart, ProdPart, DsPart, SpecOption

UPDATE (May 15, 2025):

Due to rising issues with list pricing in 16.0 Major, the following interfaces have been reverted to the 15.5 version:

override to customListPrice function in AbsPart
override to upcharge function in ProdPart
modification to basePrice function in AbsPart
modification to basePrice function in DsPart
upcharge function accounting for option specials in SpecOption

These changes were originally added to account for the new core PartSpecials system.

Impact of changes:

the new core QueryDialog will not account for special pricing for now (expected 16.0 Patch 1)
any modifications made to account for previous changes may need reversion

Those who may be affected include:

anyone who had migrated to the new core PartSpecial and/or OptionSpecial system
anyone who had migrated to the new core QueryDialog
anyone who made changes to pricing for parts extending AbsPart/ProdPart/DsPart

Anyone affected may need to:

re-test pricing to ensure accuracy
re-approach any changes made to the above interfaces
implement their own overrides to handle special pricing
wait until the core implementation for special pricing is implemented (expected 16.0 Patch 1).

The new core QueryDialog does still account for special part numbers and descriptions as well as special option codes and descriptions. The fields for special pricing have been removed for the time being.

Link to Merge Request with changes

cm.import.interop

We now officially target .NET Framework 4.8 assemblies for CM interop. As there are no version compatibility changes or behavioral changes, there should be no action required from your end. Note that Windows 10 and 11 has shipped with .NET Framework version 4.8 since 2019, and Microsoft officially has no plans to remove it as of September 2024.

We have also resolved an issue with COM interop type lookup when using certain system libraries like System.Net.Http.

cm.win

Deprecation of Old UI

The old UI in CET is now deprecated and enters maintenance support period. This implies the following:

New UI is now the default UX for all users.
The toggle to switch over to old UI is now removed by default.
No more feature / enchancements will be done for old UI.
Only critical / blocking issues for old UI will be fixed.
Issue will not be fixed if issue is not reproducible in new UI.
Code for old UI persists until 17.0, and unused components will be deprecated moving forward.