3309638 - CLR Module Breaking Changes

After the 2402 release of SAP CPQ, the usage of CLR module will be disallowed.

SAP SALES CLOUD CPQ

The decision to forbid usage of CLR module considers the damage that misuse for this feature can cause on CPQ environment, considering this was allowing to import third part libraries used in CPQ and .NET built-ins, many of the current importing of namespaces through CLR also have an alternative on the system. In addition, this goes in the direction of CPQ development, which is to provide a cohesive set of tools to build scripts with IronPhyton and CPQ APIs.

This will not take affect at existing scripts, meaning all current scripts using CLR module will not break. This will take affect in new scripts and if any modifications are needed in older scripts, which will not be allowed to save unless CLR modules are deleted.

Development team provided a set of alternatives for most used CLR importing, they can be found in page below:

• Alternatives to CLR Module Import - https://help.sap.com/docs/SAP_CPQ/7fc27540a0f14bd1a10b639117a9d4d7/210211e2ddd84124ad23c08ab4e043b3.html?version=latest
• Development team is working to provide all alternatives based on existing models.

CPQ, CLR, Import, Scripting, Deprecation , KBA , CEC-SAL-CPQ , Sales Cloud CPQ , Product Enhancement