Loading
Ongoing maintenance for Salesforce HelpRead More
Get Started with Communications, Media, and Energy & Utilities (CME)...
Limitations for the CME MP and RC Coexistence

Limitations for the CME MP and RC Coexistence

Running CME MP and RC on a shared org introduces limitations around account-level assetization, managed-package triggers, and platform behaviors. Behaviors such as global search and platform events are inherently org-wide and cannot be scoped per application. Most limitations carry no functional impact today; interim guidance and workarounds are provided where available, considering the remaining items for future validation.

Required Editions

Available in: Classic and Lightning Experience
Available in: Enterprise, Unlimited, and Developer Edition
Limitations Recommended Interim Guidance
Assetization across accounts - Submitting a CME MP order to an account that holds RC assets fails. The reverse works. This is driven by account data and applies under both operating models. Maintain separate accounts per engine, one for CME MP and one for RC. The exception is an account that already has RC; you can add CME MP to it.
Managed package orphan child records - A managed trigger creates extra child records per product regardless of apps (CME MP and RC). No functional break, but adds rows to managed-package tables. No workaround yet. No functional impact.
Managed package admin jobs without an app (CME MP and RC) filter. A few jobs operate on all records; subscribers cannot modify their queries. These jobs update only CME MP specific fields, so there is no RC functional impact. No workaround yet. No functional impact.
Managed-package triggers under a user with no CME MP license — may run and reference fields outside the user’s access and log silent errors; no functional impact is expected. Behavior can vary with your configuration — validate in your environment.
Managed-package triggers cannot be disabled per app (CME MP and RC) - They fire on shared records in every context. Make custom automation source-aware.
Related lists on shared parents are app-agnostic by default.

Use paired, record-type-filtered related-list components for CME MP and RC.

Move, Add, Change, Disconnect (MACD) scenarios currently not verified. Validate it in your customer specific org. To be planned subsequently.
Standing platform behaviors (Salesforce-native) - Global search is org-wide and not application-aware; standard list-view buttons cannot be made application-aware; PricebookEntry has no record type; platform-event subscribers cannot be application-scoped and have no cross-application ordering guarantee. Design the boundary through configuration patterns. Refer to individual sections above.
 
Loading
Salesforce Help | Article