Dsum Function in Excel

What this does

The D-functions — DSUM, DGET, DCOUNT, DAVERAGE, DMAX, DMIN — aggregate a table according to conditions written in a separate criteria range rather than in the formula. That is their distinguishing feature and their remaining advantage: a user can change the conditions by typing in cells, without editing a formula, which suits a controlled report handed to non-technical colleagues. Criteria on the same row combine with AND, on different rows with OR — which SUMIFS cannot express at all. The cost is a criteria range that must be maintained and whose headers must match the table exactly. For most work SUMIFS or FILTER is simpler. The same idea underpins a lot of everyday Excel work, so the few minutes spent getting it right here pay back across every sheet you build afterwards. Treat it as a pattern, not a one-off, and it stops being something you look up and starts being something you reach for. For “dsum function in excel”, the reliable version is a short checking loop, not just the first command that appears to work. Run it on a deliberately small range first, watch how the affected formula change, and only then apply the same setup to the full sheet. When a formula is involved, keep the inputs labelled beside it, reference cells instead of typing values, and apply number formatting only after the result checks out. That is what makes a calculation you can defend to a CFO or an auditor useful in real work: repeatable, auditable, and not dependent on memory or luck.

A worked example

A table in A1:E500 with headers, and a criteria range in G1:H2 holding "Region" and "West": =DSUM(A1:E500, "Revenue", G1:H2) totals Western revenue and updates the moment someone edits G2. OR logic that SUMIFS cannot do: put "West" and "East" on separate criteria rows. Retrieving a single matching value: =DGET(A1:E500, "Revenue", G1:H2), which errors if more than one row matches. The database functions put the conditions in cells rather than in the formula, which is what makes a report safely editable by someone who should not touch formulas. A practical tip before you scale it up: build it once on a small block of test data, confirm the number against the tool on this page, and only then point it at your real sheet. That one habit catches almost every mistake while it is still cheap to fix, long before a wrong figure reaches a report or a colleague.

In Google Sheets

If you are in Google Sheets rather than Excel, the good news is that the formula shown here is identical and the workflow barely changes — menus sit across the top instead of in a ribbon, and a few function names differ slightly, but anything you build here moves across with little or no rework. Nothing on this page is behind a login: the tool runs entirely in your browser, the formula is shown in full with one-click copy, and the steps work the same on Windows and Mac. That is the whole promise here — the exact answer, a way to prove it on your own numbers, and just enough context to make it stick. If you take one thing from this page on “dsum function in excel”, make it the habit rather than the keystrokes: set the problem up with labelled inputs, reference those cells, and let Excel do the recomputing. Bookmark the page for the syntax, but do the example once in a blank sheet and check it against the tool above — five minutes of hands-on practice fixes the method in memory far better than re-reading, and it surfaces the small snags while they are still harmless. After that the technique is genuinely yours: faster than searching for it again, and reliable enough to drop into work that other people depend on.

Common mistakes

• Omitting the header row from the database range, which is required and not optional.
• Criteria headers that do not match the table headers exactly, which silently matches nothing.
• Using DGET where several rows match, which returns #NUM! — it is strictly single-value.

Frequently asked questions