You Ran a Pivot Table and the Numbers Look Wrong — A Practical Guide to Foundry Contour

You run a pivot table and the numbers look wrong — the problem is usually somewhere upstream, not in the last step

If you’re used to Excel pivot tables, Contour feels familiar at first

“Isn’t this just an Excel pivot?” is a common first reaction to Foundry’s Contour. On the surface, it looks similar — drag in data, pick rows and columns, choose an aggregation, get a table.

Used it for a while and there’s a real difference. An Excel pivot table shows you one final result. How it got there, what got filtered out along the way, stays hidden. Contour doesn’t work that way — every filter, every join, every aggregation becomes its own standalone step called a Board.[1] Think of a conveyor belt: raw material (your source data) moves down the line through a series of stations (boards), changing shape at each one, and you can stop at any station to check what the product looks like right now.

25 boards, sorted into four groups

The official Contour docs define 25 board types.[1] You don’t need to memorize all of them — grouped by role, they break down like this.

On the conveyor belt, you’d pass through “filter & clean” stations first, merge with other material at a “combine” station if needed, then shape the final output at an “aggregate & visualize” station. You can slot a “verify” board in after any of them.

When the numbers look wrong, don’t start by suspecting the last board

When a pivot result looks off, the instinct is to stare at the last board (the Pivot Table). The official guidance actually points the other way.[2]

• Drop a Table board in between steps. Check whether a new column computed correctly, or whether the previous board did what you intended.
• Switch to the table panel. Click “Show table” to see the actual data as you apply each board — especially useful while writing Expressions.
• Add a Histogram board. A quick look at how values distribute across categories tells you fast whether your filtering actually did what you meant.

In other words: put an inspector at every intermediate station on the belt, not just the end. If you only look at the final output and call it “wrong,” finding where on the belt it actually went wrong takes much longer.

Pivot tables sometimes only show you part of the picture

Here’s something that surprises a lot of practitioners. Per the official FAQ, pivot table previews cap out at the first 100 columns or 10,000 values to protect performance.[3] The aggregation itself runs over the full dataset — what’s capped is just what’s displayed. To see the complete result, you switch to the “Switch to pivoted data” option to move to the fully-computed pivot.[3] Worth knowing on top of that: exporting directly from Contour hits a 100,000-row limit[3] — for anything larger, save the result as a Dataset instead of using Export.

What real users are actually frustrated by

Palantir’s developer community has a thread that goes right at the pivot table board’s limitations. One user put it plainly:

“The pivot widget today is very limited in its capability — sometimes it is more pain than the value it delivers.”[4]

The specific complaints:[4]

• No support for calculated fields
• Can’t filter or sort within the result itself
• Reusing a value is so awkward you often have to inspect the browser console to copy it
• No row-level conditional formatting

A Workshop team developer responded in the thread with plans for “more pivot table investment in T3 and 2025.”[4] So this isn’t a case of users missing something — it’s a real, acknowledged gap. If you need a calculated field today, the practical workaround is building the calculated column with an Expression board before the Pivot Table board, not inside it.

A practical order to work through it

1. Decide what question you’re answering before you start. “Compare this metric by region” and “trace why this number looks wrong” call for different first boards.
2. Stack filter/clean boards first. Narrow to what you need with Filter and Expression before you aggregate. Doing it in the other order makes it easy to forget a condition you meant to apply.
3. Bracket aggregation boards with Table or Histogram checks. This matters especially for boards like Pivot Table where the preview only shows part of the result — confirming the data going in is correct saves time tracing problems later.
4. Build calculated fields with Expression before the pivot board, not after. Knowing upfront that the pivot board itself has no calculated-field feature saves you from redesigning midway through.
5. If the result exceeds 100K rows or needs to be reused, save it as a Dataset instead of exporting. Most people discover the export limit only after hitting it.

Where this leaves things

The real difference between Contour and an Excel pivot table isn’t the feature list — it’s the structure. Excel shows you one result; Contour stacks the path to that result as boards you can pause at, one at a time. The pivot table board’s functional limits (no calculated fields, partial previews) are real constraints, not user error — knowing them upfront and routing around them with an Expression board is the path of least friction in practice.

FAQ

Q. Do I need to know SQL to use Contour? No. Most analysis is doable point-and-click by stacking boards. Complex calculations do require learning Contour’s own expression language.

Q. My pivot result looks wrong — what should I check first? Start with the filter and join boards before the pivot, using Table boards to verify each — not the final pivot board itself. The root cause is usually upstream of the aggregation.

Q. Is there really no way to add a calculated field? Not inside the Pivot Table board itself. Building the calculated column with an Expression board before stacking the pivot board gets you effectively the same result.

Q. Contour is slow on large data — what helps? The official FAQ recommends using well-partitioned datasets instead of raw CSVs and materializing intermediate results as datasets so your analysis path doesn’t get too long.[3]

References

[1] Palantir, Contour • Boards • Board descriptions, Foundry official documentation.

[2] Palantir, Contour • Boards • Verify results, Foundry official documentation.

[3] Palantir, Contour • FAQ, Foundry official documentation.

[4] Palantir Developer Community, Pivot Widget: Rework to make it excel equivalent — real user forum thread with an official Palantir response.

Keep reading

• Object Explorer vs Quiver vs Contour: Choosing the Right Tool
• I Tracked a Churn-Risk Customer Without Writing a Line of Code — A Practical Guide to Palantir Insight

Related on Apollo

• What Is Palantir Apollo? Automatic Updates Are Great — Until They Aren’t