Salesforce standard behavior doesn’t isolate products by app (CME MP and RC), which cause confusion between CME MP and RC records. Record types, app-specific Lightning pages, and custom list views to keep the two product designs (CME MP and RC) clearly separate.
Required Editions
| Available in: Classic and Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Edition |
Findings
- Standard list views on product show every record regardless of the current app (CME MP or RC). This implementation is obvious Salesforce behavior but can be confusing for end users.
- Standard list view buttons are org-wide. A New Product action from a CME MP app list can still create a RC record type product unless the create action is overridden.
- Product names collide easily. Nothing prevents a CME MP and an RC product from sharing a name, making global search results ambiguous without a naming convention.
- Clicking a product in the standard listing opens the app-specific record page, if it's defined for the current app (CME MP or RC).
- Record pages are associated with the correct app (CME MP or RC). The CME product Lightning page is assigned to CME MP apps (Product Designer, Industries CPQ, and Pricing Designer), and the RC product page to RC apps (PCM, Price Management, RC). This prevents clicking through to the wrong page.
- Record types alone are sufficient to drive layout and Flexipage variation on the record detail view.
Guidelines
- Keep product design app-specific. Don't work on Enterprise Product Catalog products in the PCM app, or vice versa.
- The product's record type is the primary differentiator for the app (CME MP or RC) which owns it.
- Product design is an app-scoped activity such as catalog structure, product hierarchy, attribute model, and validation rules need to live inside the owning app.
- Agree on a naming convention during the product and catalog design phase as an optional readability aid for separating EPC and PCM artifacts.
Best Practices
- Use only the app-specific and related apps for RC: PCM (Product Catalog Management) and CME MP: Product Designer.
- Create separate records for Pricebook, Products, and many such entries for each app (CME MP or RC) even when they logically represent the same thing.
- Be deliberate about the record type at creation: CME MP to its OOTB record types and RC to its record types (Technical, Commercial).
Solutions
- Build per-app (CME MP or RC) custom listing pages with a built-in record type filter. Assign each to the correct Lightning app and provide a dedicated New button pointing at the correct create action.
- Assign the right record types to profiles for CME MP user and RC user so only the applicable record types appear at creation time.
- Where products appear as a related list, use two LWCs for CME MP products or RC products filtered by record type rather than one mixed list.
Limitations
- Standard list view buttons such as New or Import can’t be app-aware, so custom LWC pages are the only fix.
- Global search returns products from both apps (CME MP or RC) regardless of the current app. This is Salesforce-native behavior and can’t be changed.