Ever tried to explain a junction object to business users prior to implementing?
Struggle to find the right example because they can poke holes in any real business example?
Ever feel like you might as well be explaining nuclear physics to a wombat?
I want to propose one that has yet to fail me
I saw this request come up again on the Salesforce Community last week and thought that there must be a way to solve it. This is something I see all the time and is a common request.
I believe that much of what I’ve done here can be completed using the Process Builder but I decided to use Andy Fawcett’s Declarative Lookup Rollup Summaries instead because as of right now that’s what I’m more comfortable with. For those that want to try this with Process Builder and Flows, take a look at Michael Gill’s solution and see if you can get a hybrid version going. Hopefully I’ll find some more time soon and can take a stab at that as a follow-up post to bring the solution completely in-house
If my title is unclear, I’m building a Wine App for my own use to track the wineries my wife and I visit, the wine we buy, and the wine we drink. So far I’ve covered off my initial planning in Part 1, and the changes I had to make in Part 2 to adjust for some limitations. I want to get this thing off the ground so that I can get everything into a system, so what I’ve been working on is getting all the fields ready, and any other setup that I’ve had to work on. In this post I want to talk a little bit about creating fields for other reasons – ie not just for the page layout. I want people to understand that a lot of bringing value is showing the business what they don’t know, and fields only for reporting, or only for related lists are a great way to do this.
As I touched on a few weeks ago, one of the great things about a developer org is that no one is around to see you screw up. The problem with this plan is that when you blog about what you are planning to do before building it, people know that you screwed up. For people who haven’t been down this path before, welcome to prototyping requirements.