. This has me intrigued as I can then have Process Builder be the center for all automation triggers. And a way to stay in the realm of clicks.
The org I have this in mind for does not have
#DLRSinstalled yet and wondering so it got me thinking, is Flow a respectable replacement to using DLRS?
Wonder if anyone else has gone the route of building rollups via flow? And in the true spirit of clicks vs. code, would there be a performance advantage to using DLRS which is housed in Apex vs using Flow
I know this all depends on the use cases. So continuing on the org in mind - Say I wanted to create 10-20 rollups in a org across 4-5 objects. The rollups mostly being count or sum with a filter or two for each.
Reading blogs like this by @david:
https://www.sfdc99.com/2018/01/22/workflow-process-builder-flow-apex/ make me think it's best to stay with DLRS as apex has better performance. Thought I'd throw the question out there to get the click vs. code thoughts.@Deanne Walters +++
I can attest to how easy DLRS is to maintain and use from a non coder perspective. I mean all the click configuration is all apex at its core?
