MetaLens360Help Center

Find a component across orgs

Component Presence shows which of your orgs contain a component and where its version differs from the majority, using each org's last synced metadata.

Updated in Drift detection & comparisons

Overview

Sometimes you don't need a full comparison — you just want to know "Which orgs have this Apex class, and is it the same everywhere?" Component Presence (page title Cross-Org Component Presence) answers that in seconds.

It reads each org's last synced metadata and compares content fingerprints (hashes). It makes no live calls to Salesforce, so it is fast and safe to use as often as you like.

You'll find it in the sidebar under Process & Flow → Component Presence.

Before you start

  • The orgs you care about must have completed at least one sync. Orgs with no synced metadata are skipped. See Run your first sync.
  • Results are only as fresh as each org's last sync. Re-sync an org first if you need today's state.

Steps

  1. Open Process & Flow → Component Presence.
  2. Optionally choose a metadata type in the type filter (it starts on All types). Narrowing the type makes the list easier to browse.
  3. Click the search box to browse components, or type at least two characters of a name.
  4. Pick a component from the list, or keep your typed text, and click Find (or press Enter).
  5. To limit which orgs are searched, click change next to "Scope: all N orgs with synced metadata", then click org chips to select them. Click hide to collapse the list, or reset to go back to all orgs.
  6. Read the results grid: one row per matching component, one column per org.

How to read the results

The header reads like "{n} matches for … across {m} orgs", and a "{n} drifted" chip appears when versions differ.

MarkMeaning
Green checkThis org matches baseline.
Split arrowdrifted — this org's version differs from the baseline.
Dashabsent — the org doesn't have the component.

The baseline is the majority version: the content shared by the most orgs. It is not a fixed "golden" org. Orgs holding the baseline version are tagged base on drifted rows. Ties are broken by cloud, then org type, then name.

Example

A support ticket mentions OrderTriggerHandler. Priya searches for it and sees it present in five orgs. Four match; acme-uat is drifted. That tells her UAT holds a different version, so she runs an Org vs Org comparison of acme-uat against acme-prod to see the exact lines.

FAQs

Does "drifted" mean the org is wrong?

Not necessarily. It only means the org differs from the majority. A newer version under test in UAT will show as drifted until it reaches the other orgs.

Can I see the actual differences here?

No. Component Presence shows where versions differ. To see line-by-line changes, run a comparison — see Run a metadata comparison.

Why isn't one of my orgs listed as a column?

It has no synced metadata, or it is outside the scope you chose. The results header notes how many orgs were skipped.

Troubleshooting

"Enter at least 2 characters."

Type a longer search term, or pick a component from the list.

"No components matched in any org's synced metadata."

Check the spelling and the type filter. If the component was created recently, sync the org first.

Your search matched too many components to show. Add more of the name or choose a type.

Was this article helpful?

Related articles