Here’s a real-world Salesforce scenario I recently had with a client.
The client needed to record meetings with their end clients. The meeting summary tracked the subject, summary, date, status, related contact(s), and related organization. It also needed to record the internal team (a collection of users) present at the meeting.
Tasks seemed like an appropriate object for this requirement. This is because the summary was only recorded once and minimal follow-up would occur. The only challenge was, tasks can only be related to a single user and the requirement was to associate it to multiple users.
Reporting is a consideration, as the client wanted to know how many meetings each user attended that year.
As a “good enough” Salesforce consultant, how would you solve this?
I’ll share my approach tomorrow.
The takeaway
When you reach the limits of out-of-the-box functionality, you need to start thinking outside-the-box. Just don’t wander too far outside, as you may get lost.