Why Notion Formula Output Differs in Calendar View Tooltip vs Page

You have a Notion database with a formula property. In Calendar view, when you hover over an item, the tooltip shows a different value than what appears on the actual database page. This mismatch can cause confusion when you rely on the tooltip for quick data checks. The root cause is that Notion’s Calendar view tooltip displays the formula result using a simplified rendering engine that does not support all formula functions and formatting. This article explains why the discrepancy occurs and provides a definitive method to align the tooltip output with the page value.

Why the Calendar View Tooltip Uses a Different Formula Engine

Notion’s Calendar view is optimized for performance. When you hover over an event, the tooltip must load instantly from a cached or pre-computed data set. To achieve this speed, Notion uses a stripped-down interpreter that can handle basic property lookups and simple calculations but cannot execute the full formula grammar. Functions like formatDate require a locale-aware formatter that the tooltip engine does not include. As a result, the tooltip may show the raw timestamp number instead of the formatted date string.

Another contributing factor is the way Notion serializes formula results for the tooltip. Complex data types — such as arrays, objects, or multi-line strings — are flattened or truncated. For example, a formula that returns a list of tags separated by line breaks may appear as a single line with commas in the tooltip. The page view, by contrast, renders the full formula result using the main database renderer, which respects all formatting and type conversions.

Additionally, the tooltip engine does not support cross-database lookups or relation traversals. If your formula uses prop("Related").prop("Name"), the tooltip will show an empty value or an error. The page view, however, resolves the relation and displays the linked property value correctly. Understanding these technical limitations is the first step toward a reliable fix.

Steps to Align Formula Output in Calendar Tooltip with Page View

The following method creates a dedicated formula property that produces output the tooltip can display correctly. This approach does not change the original formula but adds a parallel property for tooltip consumption.

1. Open your database and identify the problem formula
   Navigate to the database that contains the formula property showing the mismatch. Click the + button in the table header to add a new property. Name it something like “Tooltip Safe Formula”. Set the property type to Formula.
2. Simplify the original formula for the tooltip engine
   In the new formula property, write a version of your original formula that uses only the following supported functions: prop, empty, not, and, or, equal, unequal, larger, largerEq, smaller, smallerEq, add, subtract, multiply, divide, pow, mod, unaryMinus, unaryPlus, concat, join, slice, length, replace, replaceAll, test, if, format, and toNumber. Avoid formatDate, dateAdd, dateSubtract, dateBetween, timestamp, fromTimestamp, min, max, abs, cbrt, ceil, exp, floor, ln, log2, log10, round, sqrt, sort, reverse, map, filter, every, some, first, last, at, id, name, and count. For example, if your original formula is formatDate(prop("Start"), "MMM D, YYYY"), replace it with prop("Start") — the tooltip will show the raw date, but at least it will be consistent with the page view’s date property.
3. Test the new formula in Calendar view
   Switch to Calendar view. Hover over an event and check the tooltip. It should now display the same value (or a simpler equivalent) as the page view. If the mismatch persists, further simplify the formula by removing any if statements with nested functions. Replace if(prop("Status") == "Done", "Completed", "Pending") with prop("Status").
4. Hide the original formula from Calendar view (optional)
   If you prefer to see only the tooltip-safe value, right-click the original formula column header and select Hide in Calendar view. This removes the column from the Calendar view layout but keeps it visible in other views.
5. Use a Rollup as an alternative for cross-database formulas
   If your formula relies on a relation, create a Rollup property instead. In the related database, add a simple formula that produces the value you need. Then, in the original database, create a Rollup property that pulls that value. The Rollup property will display correctly in both the tooltip and the page view because Rollups are pre-computed and cached.

If the Calendar Tooltip Still Shows Wrong Values After the Fix

Tooltip Shows a Timestamp Number Instead of a Formatted Date

This happens when the formula uses formatDate. The tooltip engine cannot process date formatting functions. Replace the formula with a plain date property reference. If you need a formatted string, create a separate text property and manually enter the date string, or use a Rollup from a database that stores the date as text.

Tooltip Shows an Empty Value for a Relation-Based Formula

The tooltip cannot resolve cross-database lookups. Create a Rollup property that pulls the target value from the related database. For example, if you want to show the project name from a linked project, add a Rollup in the original database that rolls up the project name. The Rollup will appear in the tooltip because it is a pre-computed value.

Tooltip Shows a Truncated or Incorrect Number After Rounding

The round function is not supported in the tooltip engine. The raw floating-point number appears instead. Use format("%.2f", prop("Amount")) only if you are certain the tooltip engine supports format — in practice, it does not. Instead, multiply the number by 100, use toNumber to truncate, then divide by 100. Or simply accept the unrounded value in the tooltip and rely on the page view for the precise number.

Formula Functions Supported in Calendar View Tooltip vs Page View

Function Category	Page View (Full Support)	Calendar Tooltip (Limited)
Date formatting	formatDate, dateAdd, dateBetween	None; raw timestamp displayed
Mathematical rounding	round, ceil, floor, abs	None; raw float displayed
String concatenation	concat, join, replace	concat and join work; replace may fail
Conditional logic	if with nested statements	if works only with simple comparisons
Cross-database lookup	prop("Relation").prop("Field")	Not supported; returns empty

The table above summarizes which formula functions behave differently. If your formula uses any function from the third column’s “None” cells, the tooltip will show a raw value or an empty result. The only reliable workaround is to create a simplified formula that avoids those functions entirely.

You now understand why the Calendar view tooltip and page view display different formula outputs. To fix the discrepancy, create a dedicated formula property that uses only the basic functions supported by the tooltip engine. For cross-database lookups, use a Rollup property instead. As an advanced tip, you can set the original formula property to hidden in Calendar view and show only the tooltip-safe property, giving you a clean and consistent interface without losing the original formula in other views.