We've added a clearer description of how view columns work in reporting to the product documentation. They are not just a visual subgrid in a record detail. They are filtered results from a chosen database that can feed into formulas.
This matters for teams that want to calculate summaries from child data without manual copying.
What this enables
A typical example is the hierarchy of company, project and task. A task holds work and costs, a project sees its tasks via a view column and formulas over them calculate hours, budget or open blockers. The company then aggregates projects via its own view column.
The result is reporting that is built on actual working records.
Where you'll see this
This principle is reflected in the product pages on databases, views and print reports. It helps explain why relations, views and formulas are one shared layer, not three separate features.
For users, this means simpler design of dashboards, reports, PDF outputs and automated checks.