OrgParityFREE TOOLS / PROBEKIT

Start here · No installation

A clear first step.
In about five minutes.

Try a fictional example to learn the workflow. Then choose a question and bring your own query exports when you are ready.

Try the walkthrough ↓

What are you investigating?

Browse all 73 investigations →

Five-minute walkthrough · Fictional data only

Compare two flow exports

You are checking whether two supplied exports describe the same flow version. No Salesforce access, files or credentials are needed for this sample.

  1. Open the flow-version workspace. Open the sample workspace in a new tab ↗. Keep this guide open alongside it.
  2. Turn on “Compare two result sets”. Then select “Try fictional sample”. Both sides are labelled fictional.
  3. Review the query steps. The definition step checks active/latest version numbers. The versions step lists exported versions and statuses. Notice the Tooling API badges.
  4. Read the comparison. The supplied sample uses different version numbers and statuses. The comparison reports differences in declared columns; it does not establish which configuration is correct.
  5. Download a summary. Select “Download findings (.txt)”. Check the fictional-sample label and the limitations. Reports omit raw result rows.
  6. Clear the investigation. Select “Clear all data” before supplying your own exports. The sample findings disappear; the downloaded file remains on your device.

What you learned: query → export → evidence → next check. A difference is a reason to investigate, not proof of a defect.

Ready for your own question?

Use an approved query tool, match the Standard or Tooling API badge, preserve every selected column and export every page. Accept each result to unlock dependent steps. The browser processes supplied results in the tab without uploading them.

Read the full usage guide · Connect the optional local MCP server

Help improve the tool

Report a reproducible problem or request an investigation. Use fictional examples only. Exclude credentials, org identifiers, client names and real exports. GitHub issues are public.