CS.SM.refreshSolutionConsole Is Not a Function on Solution Management R38 (Fixed in cssmgnt 38.0.23)

Solution

How to Confirm You Are Affected

1. Check your installed version. Go to Setup > Installed Packages and note the Solution Management (cssmgnt) version. If it is an R38 build earlier than 38.0.23, you are exposed.
2. Run a runtime check in the browser console (on a page where the Solution Console is loaded):
   • Run typeof CS.SM.refreshSolutionConsole. An affected build returns "undefined".
   • Calling await CS.SM.refreshSolutionConsole() returns TypeError: CS.SM.refreshSolutionConsole is not a function.
   • On a fixed build the call resolves and the console re-renders — when the active solution is deleted, the next solution is selected automatically.
3. Optional source check (deep verification). In the installed Solution Console React bundle (static resource cssmgnt__solution_console_react_*_chunk → cssmgnt.chunk.js), search for refreshSolutionConsole, getNextActiveSolutionAfterReload, and rerender-helper. On an affected R38 build all three return 0 occurrences, while the R38 re-render internals (setUIDelegate, _reRender, loadTimeStamps, BasketSetActive) are present.

Why the Unsupported Workaround Should Not Be Used

CS.SM.uiDelegate.rerender(true) may appear reachable at JavaScript runtime, but it is not a supported substitute on the R38 line. Do not build against it, for the following reasons:

• uiDelegate is declared as a private member — it is only reachable at runtime because TypeScript private is a compile-time-only restriction.
• Its interface is typed rerender: () => void — it does not accept the reload-basket parameter.
• The R38 _reRender only performs loadBasketThenPublish followed by a navigateToComponent on the current active component. It does not contain the deleted-active-solution handling, so after deleting the active solution it re-navigates to the now-stale component. This path also contains a stale-closure regression that causes it to re-navigate to a stale component.

Resolution Steps

1. Upgrade Solution Management to 38.0.23 or later — the R38 build where the public API was restored (package version ID begins with 04tWV0...). This build:
   • Restores CS.SM.refreshSolutionConsole(reloadBasket = true) as a public method.
   • Restores the deleted-active-solution re-render logic (selects the next solution, or the empty state, after the active solution is deleted), matching the R37 behavior.
   • Preserves the existing R38 concurrency fixes (per-solution timestamps, basket-load race guard, and BasketSetActive ordering).
   • Documents the method in the JS API documentation that ships with the package.
2. Clear caches after the upgrade.
   • Clear the Solution Management and Pricing Service caches.
   • Clear your browser cache and reload the Solution Console page so the browser does not serve a cached copy of the old console bundle.
3. Verify the fix at runtime.
   • In the browser console, run typeof CS.SM.refreshSolutionConsole → expect "function".
   • Execute the Change Solutions path end-to-end: open Change Solutions → close the modal → the console refreshes → the automatic Add to MAC Basket step completes — all without the TypeError.
   • Confirm in Setup > Installed Packages that the cssmgnt version is 38.0.23 or later.
4. Verify the fix in source (optional). Re-scan the installed cssmgnt.chunk.js for refreshSolutionConsole and getNextActiveSolutionAfterReload — both should now be present.

Availability by Release Line

If you run multiple release lines, be aware that this API has different availability per line:

• R36-MR1: available in 36.14.11 and later.
• R37: available in 37.4.16 and later.
• R38: available in 38.0.23 and later (earlier R38 builds are affected).

If a plugin must run unchanged across lines, make sure each installed line is on a build that includes the API before relying on CS.SM.refreshSolutionConsole().

Note: CS.SM.refreshSolutionConsole() is an asynchronous method and returns a Promise — always await it (or use .then()) in custom code. For broader guidance on async CloudSense Solution Management API methods, see Solution.getComponentByName Not A Function: Missing Await for Async Call.

Note: If you still see the error after upgrading to 38.0.23+ and clearing caches, confirm the upgrade actually completed (check the package version in Setup > Installed Packages) and that the browser is not serving a cached copy of the old console bundle. If a sandbox was refreshed from Production, it reverts to production package levels — re-install the R38 package set before re-testing the Change Solutions path.