Jasper van Voorst - 7 months ago
We have this requirement a lot. Since it's not standard functionality we use RollupHelper app for it https://appexchange.salesforce.com/appxListingDetail?listingId=a0N30000009i3UpEAI That does the job perfect. Without any limitiations.You can create rollups from every related object with all fieldtypes as source.
Menachem Shanowitz - 7 months ago
I recently created a free app that provides a way to do this, Unleash Your Formula. https://appexchange.salesforce.com/appxListingDetail?listingId=a0N4V00000DVyH4UAL
All it does is copies and syncs a formula field to a non-formula field (created for this purpose). This allows you to circumvent all formula restrictions by using the synced non-formula field.
Niklas Bergh - 8 months ago
In response to @Mark Cira below. Yes, you are correct that DLRS can be used to achive this (and we use it for sure as there are no great alternatives).
But.. the problem with DLRS comes when you for some reasons need to run the rollup in 'Realtime' vs scheduled (typically since the users would need fast feedback as they work in the system), then you are going against many of Salesforce's own recommendations around 'avoiding custom logic on objects which are numerous, such as line-items', because then tight governor limit will be likely to start giving you plenty of grief.
Also, and this is a very nice co-incidence, the feature around 'Where is this field used?' which is marketed by @Vladimir Gerasimov from Salesforce a year ago in relation to this thread does not play nicely with DLRS. So you end up in annoying situations a'la: So what in my instance actually populates this field then? The SF 'Where is this field used?' feature says that nothing is using it??? So you end up feeling a need to populate the comment on many fields with a 'Please note that this field is managed by the DLRS rollup called XXXX', and thereafter you have to remember to manage this type of information as well as your logic, so the burden quickly becomes higher..
And well... the solution probably is to allow the native rollups to do some really basic proper things such as rolling up on formulas