Salesforce Docs Portal

Opportunity, Quote, and Order Capture

The record type is the differentiator for Opportunity, Quote, and Order. CME MP uses its out-of-the-box record types, while customer implementations must create net-new custom record types for RC. This is necessary because RC has no out-of-the-box record types for these objects, yet the new record picker forces a selection.

Required Editions

Available in: Classic and Lightning Experience
Available in: Enterprise, Unlimited, and Developer Edition

Findings

  • Opportunity, Quote, and Order listings are app (CME MP or RC) agnostic by default.
  • Creating one of these records triggers the standard record type picker, which shows CME MP record types even in the RC app.
  • Global search returns records from both CME MP and RC regardless of the current app context. This is native Salesforce behavior and cannot be changed.
  • Reports return records from both CME MP and RC unless the report includes a filter that differentiates between CME MP and RC records.
  • Opening a cross-app record, such as an RC record in the CME MP app or a CME MP record in the RC app, may render silent without an error, but the record details might appear broken. Users may not realize what went wrong.
  • By using the same pricebook in both RC and CME MP doesn’t break pricing. RC uses PricebookEntry and ProductSellingModel, while CME MP uses PriceList and PriceListEntry.

Guidelines

  • Use the correct app for the intended scope.
  • Don’t access CME MP records in RC apps or RC records in CME MP apps.
  • If there is separate users, assign separate users for CME MP and RC so the assigned app controls what each user can create. Apps are assigned through a profile or permission set. In shared users, this control doesn’t exist, so the differentiator and validation rules must enforce it instead.
  • Every Opportunity, Quote, and Order must be classifiable to either CME MP or RC at creation time through a record type. No shared records are allowed.
  • Record context must stay within one scope end-to-end. A CME MP opportunity must not produce an RC quote, and an RC opportunity must not produce a CME MP quote.
  • Listing pages record pages, and creation actions must all be scoped either as CME MP or RC. Avoid leaving them as standard.
  • Custom reports must include explicit CME MP and RC segregation filters to avoid cross-app data mix ups.

Best Practices

  • Assign record types per app at creation that CME MP uses OOTB record types. RC uses custom record types.
  • When by using the standard New action, ensure that the selected record type belongs to the correct scope (CME MP vs. RC).
  • Use a custom Lightning page for Opportunity, Quote, and Order listings filtered by record type.
  • Maintain cart-navigation continuity for an Opportunity and its resulting Quote and Order must stay within the same scope (CME MP or RC).For example, a single Opportunity can’t carry line items from both apps as it breaks pricing and orchestration downstream.
  • Use separate accounts for CME MP and RC if possible.
  • Use separate pricebooks per app. When selecting a pricebook, ensure it belongs to the correct scope (CME MP and RC).

Solutions

  • Create a dedicated RC record type for Opportunity, Quote, and Order.
  • Build per app (CME MP vs. RC) custom listing pages with a record type filter, assigned to the correct Lightning app, each with a dedicated New button. This makes sure that the intended record is created.
  • If you intend to use a shared account between CME MP and RC, use separate related lists or LWCs on the Account page for CME MP Opportunities, Quotes, and Orders, and RC Opportunities, Quotes, and Orders. Each list filters by record type instead of using a single mixed list.

Limitations

  • Product hierarchy and configuration UI are app-specific, opening a CME MP record in the RC app renders the header but not the hierarchy or configurator.
  • The standard new action forces the record type selection page and can’t be changed.
  • Global search isn’t app-aware, only app-owned surfaces such as listing pages, detail pages, and related lists can be app-scoped.
  • A customer with both CME MP and RC activity requires separate accounts, explicit labeling, or separate related sections where the platform doesn’t natively partition account-level activity by app.