Salesforce Docs Portal

Common Entities Access

This section covers the common entities access in general some of these might be covered in the individual sections previous.

Required Editions

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

Findings

  • Standard list views aren’t app-specific. Users can see both CME MP and RC records together unless separate CME MP and RC custom listing pages are in place, which show only their respective records.
  • Detail pages behave correctly when record types and visibility rules are configured.
  • All the shared objects show the same app-agnostic list behavior. The fix pattern is uniform across all of them.
  • Pricebook Entry has no marker of its own, filters through the parent Pricebook.
  • Global search and reports remain cross-app for the entities or objects even when their respective pages are scoped.
  • Detail page tab sets and quick actions are gated by record type and app context.
  • The Asset object has two standard, app-specific asset views (CME MP and RC). Both read the same shared Asset table for an account, but the RC view hides CME MP assets and vice versa.

Guidelines

  • Users of each app (CME MP and RC) should ideally see the records their app (CME MP and RC) owns.
  • Each shared object should ideally be filterable by source app (CME MP and RC), using the differentiator mechanism defined above.
  • The listing surface for every shared object should ideally be a per-application (CME MP and RC) custom page, avoiding exposing standard list views to end users.
  • Related lists on shared parents such as Account, should ideally be scoped per app (CME MP and RC). Create a custom list under the parent for the related shared objects, split between CME MP and RC.
  • Custom reports and dashboards on shared sObjects should ideally carry an explicit CME MP vs. RC filter.
  • If possible display the marker (CME MP and RC) prominently on the record header.

Best Practices

  • Maintain separate CME MP Reports and RC reports folders.
  • Override the standard New and Import buttons per app (CME MP and RC) so product, cart, and pricebook creation always respect the current app's context.

Solutions

  • Per-application(CME MP and RC) custom listing pages, one per object per app, filtered on its marker.
  • Related-list components on Account or Contract or Opportunity, replace standard products, assets, orders, or quotes related lists with paired components (CME MP Products and RC Products, etc.).
  • Assign each record page to its owning app (CME MP and RC) and any relevant designer app.
  • Maintain separate CME MP Reports and RC reports folders, each carrying the corresponding origin-app filter.

Limitations

  • End-user reports on shared objects return cross-app rows unless an explicit app (CME MP and RC) filter is applied; report authors must be trained on this.
  • Standard list views can’t be made app-aware (CME MP and RC), custom listing pages are the only reliable fix. Users can’t rely on the default All Products or All Assets list views inside either app (CME MP and RC).
  • Global search returns cross-app rows regardless of the current app (CME MP and RC). This is Salesforce-native behavior.
  • Every new shared object requires a dedicated pair of custom listing pages (CME MP and RC) with quick-action overrides.