Skip to content
Community · with Salesforce Insights in 5 Minutes

Salesforce news

The best of the Salesforce ecosystem, filtered for you every week by Grzegorz Skaruz, plus the articles the ORGanizer community suggests. Vote for what matters to you and say what you think of it.

Suggest an article

This week’s issue · #197 18 articles · sent Tue Oct 27 · here since Thu Oct 29

Design a System of Record, Architecture Diagrams Guide, Agentforce Demand Lagging Despite Trials

From the curator, Grzegorz Skaruz: Another week, another mix of "this changes everything" and "wait, did we just agree to that?" moments in the Salesforce world.I'm digging into a practical one first: designing a proper system of record across multiple objects, because scattered data isn't a "which field goes where" problem, it's an architecture problem. Speaking of architecture, there's also a solid refresh on diagramming tools and templates worth bookmarking if you spend more time explaining your org than building it. Read the whole note

Another week, another mix of "this changes everything" and "wait, did we just agree to that?" moments in the Salesforce world.I'm digging into a practical one first: designing a proper system of record across multiple objects, because scattered data isn't a "which field goes where" problem, it's an architecture problem. Speaking of architecture, there's also a solid refresh on diagramming tools and templates worth bookmarking if you spend more time explaining your org than building it. Then there's Agentforce. Adoption numbers look great on paper, but the gap between "tried it" and "committed to it" is getting harder to ignore. I'm covering why the pilot phase is ending and what companies are actually running into now that the hype is settling. And if you're on Winter '27 prep, I've got the critical changes worth testing before they test you. Grab your coffee and dig in.

Subscribers read this issue two days before it landed here.

Articles

3 articles match · Clear filters

  1. Salesforce Insights in 5 MinutesIssue #197Reddit Discussions

    Where does your team draw the Flow vs Apex line in 2026?

    Asking where other teams draw the Flow vs Apex line these days. For a mid-sized org, simple record-triggered stuff stays in Flow, but once it has multiple loops, cross-object branches, or needs solid bulk handling, it gets harder to test than just writing a small Apex service. The tricky zone is medium-volume integrations (5-20k records) - Flow can technically do it, but error handling and retries get messy. Wants to know what's actually working for people in production in 2026 - do you keep most logic in Flow and only pull out the heavy stuff to Apex, or set your complexity bar lower than that?

    reddit.com 0 comments 1 read Read the article

  2. Salesforce Insights in 5 MinutesIssue #197Reddit Discussions

    Is Salesforce giving Claude a little too much power?

    Someone's wondering if Salesforce is handing Claude a bit too much control these days - pulling data, updating records, triggering actions, basically doing everything inside the CRM. The real question: if Claude can handle all that from its own chat, why even open Salesforce anymore? Sure, Salesforce still owns the data and permissions underneath, but it feels like Claude's becoming the actual interface people use, with Salesforce just running quietly in the background. Not sure if this is just where enterprise software is heading, or something we'll look back on and think "wait, we gave an AI THAT much access?" Curious what other Salesforce folks think.

    reddit.com 0 comments 1 read Read the article

  3. Salesforce Insights in 5 MinutesIssue #197Reddit Discussions

    I'm afraid of performing mass updates

    Mass updates on old records really freak this person out, so they tend to avoid them whenever possible. Last task was updating 81,000 records with a new payment date, but they ended up on sick leave before tackling it. Big worry is not knowing how to be sure nothing breaks, plus no clear way to roll back changes afterward. Checking every field and value across 81k records isn't realistic, and there's also fear of hidden blockers like triggers or validation rules messing things up. Basically asking for a solid, clear approach to handle mass updates safely without losing sleep over it.

    reddit.com 0 comments 1 read Read the article

News in this section is curated by Grzegorz Skaruz for his weekly newsletter, Salesforce Insights in 5 Minutes. Devs, admins and architects get the full issue every Tuesday - free, no spam, unsubscribe anytime.