How to compare two web tables using a clear matching key
A list comparison helps identify shared, added or missing records across two supplied tables. The result depends on choosing a key that genuinely identifies the same thing in both sources.
Start with the right material.
- What you provide
- two small tables visible together on one page or provided as text.
- The intended result
- Export common, only-in-A and only-in-B records using the user's key.
How the workflow works.
Define the matching key and normalization rules, then preserve the original row references. Handle duplicate keys and blank identifiers separately so they do not create misleading matches.
What to check in the result.
Check several matched and unmatched records manually. Differences in selection, update time or formatting can explain a mismatch without proving that either source contains an error.
Import the CSV with a consistent delimiter and inspect text identifiers, dates and amounts before using spreadsheet totals. Keep the original file available while checking any automatic type conversion.
Learn from the worked example.
The downloadable CSV example uses these columns: Key, Membership. Compare a complete record with the source before sorting, combining or importing your own output.
The supplied example is illustrative. It is not a recorded run on your data.
Download the example ↓Use it with your own material.
- Open the source you want to work with and activate WebAct on that tab.
- Copy the task from the hero, add any required fields or preferences, and review the proposed actions.
- Compare the first result with your source. Ask for a specific correction or refinement where needed.