Start a conversation Sign in
Start a conversation
  1. CloudSense Support
  2. CloudSense Articles
  3. Articles

Salesforce Classic: “Product Designer” Button Missing on Product Definition (Expired CloudSense Product Explorer & Designer Package)

Contents

Overview

In Salesforce Classic, the Product Designer action/button can disappear from Product Definition records when the managed package CloudSense Product Explorer & Designer (namespace cspduia) is shown as Status = Expired in Setup → Installed Packages.

This is expected behavior when the deprecated CloudSense Product Explorer & Designer package is expired/enforced in a Production org, which removes access to package-delivered UI actions. The supported mitigation is to install CloudSense Product Design Studio (recommended: CloudSense R36 MR1 / v1.10.7) and add the replacement button to the Product Definition page layout.

Solution

Issue

The Product Designer button is not visible on the Product Definition record page in Salesforce Classic, even though it is normally shown with other actions (for example: Edit/Delete/Compile/Export).

What you typically see

  • In Setup → Installed Packages, CloudSense Product Explorer & Designer shows Status = Expired (often with an expiration date, for example 10/10/2025).
  • The Product Designer action is missing from the Product Definition record page.
  • Lower environments (for example, UAT) may still show the button.

Cause

CloudSense Product Explorer & Designer is a deprecated managed package. When it is expired/enforced in a Production org, package-delivered UI actions (including Product Designer) are no longer available.

Resolution (supported approach)

  1. Stop using the deprecated package

    If your Production org is still using CloudSense Product Explorer & Designer (namespace cspduia), plan to replace it rather than continuing to rely on it.

  2. Install the replacement package: CloudSense Product Design Studio
    • Install CloudSense Product Design Studio.
    • Recommended target level for this scenario: CloudSense R36 MR1 (v1.10.7).

  3. Note: Installation links and rollout timing can depend on your licensing and release path.

  4. Add the new package button to the Product Definition page layout (Salesforce Classic)

    After installing CloudSense Product Design Studio, add the replacement button to the page layout used by your users:

    1. Go to the configuration area for page layouts (for example, Object Manager or the Classic equivalent setup path).
    2. Open the Product Definition object configuration.
    3. Edit the relevant Page Layout used by impacted users.
    4. Add the Product Design Studio / Product Designer button (from the newly installed package) to the layout’s Buttons / Actions section.
    5. Save the layout.

Why Production Is Impacted While Lower Environments May Still Work

  • Enforcement can be applied differently by org. In this scenario, deprecation enforcement was applied only to Production orgs.
  • Future sandboxes refreshed from Production can inherit the same behavior as Production, so the issue may begin to appear in refreshed sandboxes later.

Validation (Confirm the Fix)

  1. In Production, open Salesforce Classic.
  2. Navigate to Product Definitions.
  3. Open a Product Definition record.
  4. Confirm the Product Designer (Product Design Studio) button is visible again and launches correctly.

Frequently Asked Questions

1. How do I confirm I’m affected by this specific issue?
In Salesforce Setup → Installed Packages, check CloudSense Product Explorer & Designer (namespace cspduia). If it shows Status = Expired and the Product Designer button is missing on Product Definition records, you are affected.
2. Is this a CloudSense defect?
No. This behavior is expected when a deprecated/expired managed package is enforced in Production, which can remove package-delivered UI actions (such as Product Designer).
3. Why does it work in UAT/DEV but not in Production?
Enforcements can differ by org. In this scenario, deprecation enforcement was applied only to Production orgs, so lower environments could continue working until their package/license state changes. Sandboxes refreshed from Production in the future can inherit the same behavior as Production.
4. After installing CloudSense Product Design Studio, the button still isn’t visible—what should I check?
Confirm the new package’s button has been added to the Product Definition page layout used by your users. Then reload the Product Definition record page in Salesforce Classic.
5. What version was recommended in this scenario?
CloudSense Product Design Studio R36 MR1 (v1.10.7).
Choose files or drag and drop files
ai_initiated
atlas_studio
kb_automation
Was this article helpful?
Yes
No

  1. Matej Storga

  2. Posted
  3. Updated

Comments