
Quick Wins:
Portals: Account-Level Access Challenge
Your customers, linked as Contact records, can access their information via the CRM portal. @Ivan Staykov brought up an interesting use case where individual Contacts should only access records linked to their emails, while the CEO of their company should access all Contact records linked to their Account. As CRM portals are tied to Contacts, not Accounts, this setup isn’t straightforward. @Max explored options, and @Amy shared a workaround that sparked Ivan’s interest. If you’ve run into the same limitation, this thread is a must-read for practical insights.
Understanding how custom view un-enrollment works in Cadences?
Tip for targeted marketing campaigns for Contacts with closed Deals!
Developer's Corner:
Can you fetch 200+ records from a Custom View at once?
@Sam wanted to pull all records from a Custom View exceeding the 200-record limit without using pagination. @Sunderjan Siddharth clarified that COQL can fetch up to 2,000 records in a single query, and suggested using a loop to retrieve up to 100K records efficiently.Check-out the post for the full solution on handling large datasets effectively in Zoho CRM.
Make attachments mandatory before closing Deals:
@Jhonata wanted to make it mandatory to add attachments before marking a deal as Closed-Won. @Rakesh Kumar suggested triggering a Client Scripts on the Stage field update across touchpoints like the Details, Edit, and Canvas pages to check for attachments, cancel submission if none exist, and display an alert. @Pheranda Nongpiur followed-up with step-by-step guidance and shared the sample Client Script to check attachments on save. Check the full post for the scripts and detailed setup instructions!
How Marta leveraged AI and assistance from the community to automate Quote stage updates:
Kaizen:
Answering Your Questions!
(Kaizen #204) - Perform Field Updates before Blueprint transition via Client Script
Learn how to enhance your lead follow-up Blueprint by prompting users for input during Blueprint transitions and updating description field with detailed comments in Zoho CRM. Kaizen #204 demonstrates how to use beforeTransition scripts to capture comments, validate input, and maintain a running comment history. In this setup, a popup prompts users to enter a comment before each transition. If the comment is fewer than 25 characters, the transition is stopped; otherwise, the system appends the comment along with the transition name and user’s name to the Description field. This is a practical way to improve transparency and traceability in your Blueprint process. Check the post for the full code and setup!
(Kaizen #205) - Managing Picklists and Enabling History Tracking via Zoho CRM APIs
And that’s a wrap for this fortnight’s Zoho CRM Community Digest. Caught something cool we missed? Or have a favorite from this edition?
Drop it in the comments! We’d love to hear from you. We’ll be back in two weeks with more updates and community gems.
Until then, stay tuned!