When building views I find myself wanting to see derived information - most commonly another field from a relation and an aggregation of fields. For example when looking at Feature requests associated with User I might want to see User.company or User.status (Trial, Paying, etc.) instead. And honest…

I mentioned what I think is the same idea a while back, it’s similar to something Coda can do, and Michael said it should be “easy” to implement, so hopefully it comes around! [image] Migrate Entity View to Blocks Ideas & Features I know Michael addressed this, but in case…

It does look related, although the conversation was focused on Blocks, which was a bit confusing to me. Are Blocks intended to replace current Views (Table, List, etc.)? Will Table and List views stay as the basic out of the box components and Blocks are intended to be the more advanced flexible alt…

[image] Pawel_Badenski: When building views I find myself wanting to see derived information - most commonly another field from a relation and an aggregation of fields. I’m not sure I fully understand the use case you’re describing. Are you thinking in reference to a particular type of view (…

[image] Chr1sG: I’m not sure I fully understand the use case you’re describing. Are you thinking in reference to a particular type of view (Report, Board, Timeline, Table, Document…)? I’m thinking about Table or List view (but I think it applies to any view that can display Fields). [imag…

OK, understood. So would it be effectively solved if fields could be hidden in entity view? i.e. you create the formula field you need (in Table view or wherever) and it would be created as a new database field (available in any view) but wouldn’t show up on the entity view UI by default? (or any …

For the use case presented here it would be a step forward although I think it’s a bit of a workaround because: over time these ad hoc fields will accumulate and might be tricky to trim them down: “have I created that hidden field or someone else did”, “are those fields used anywhere, which views …

[image] Pawel_Badenski: I think it’s a bit of a workaround Indeed. Quick q: Is your wish that the ad hoc fields should be per-user as well as per-view? Or per-view and available for all users to see?

In my mind it was per-view and available for all users to see (ie fields are subordinate to view in terms of permission, if a user can see the view they can see the fields).

I am 100% with Pawel here. Ad-hoc fields in Rich Text/Docs (or even Whiteboard? :exploding_head:) would be a huge value-add to me. There are zillions of uses I can think of for them. Coda has this, and there are multiple other systems that implement varying degrees of sophistication in similar tools…

[image] Oshyan: Ad-hoc fields in Rich Text/Docs (or even Whiteboard? :exploding_head:) would be a huge value-add to me. That’s not quite what he’s asking for, i believe. He has asked for ad-hoc fields in views (table view, list view etc) which is a subtle difference.

Ad hoc formulas in views

Ideas & Features

Matt_Blais May 17, 2023, 10:11pm 17

Topic		Replies	Views
Formula fields that are filtered by the context they're viewed in Ideas & Features	7	134	September 5, 2025
Inline formulas Ideas & Features rich-text	18	472	March 6, 2026
Hide view : filter on view content Ideas & Features	2	30	March 19, 2026
Can't add Formula-type fields to customizable list at top of entity view Ideas & Features	2	203	April 29, 2025
Readonly only formula fields - Add formula to form Ideas & Features	0	181	March 20, 2023

Ad hoc formulas in views

Related topics